Native macOS Mihomo proxy client built with SwiftUI.
C-Rank Grade: B (Solid) - 59/100
External PR Merge Rate: 100%
Response Time: <1h
First Timer Success: 100%
marvinli001/ClashMax has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in marvinli001/ClashMax respond to incoming external pull requests in approximately 0.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 59.5 places marvinli001/ClashMax in the B tier.
The external contributor pull request merge rate for marvinli001/ClashMax is 100.0%, based on public PR activity from non-core contributors.
marvinli001/ClashMax currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in marvinli001/ClashMax. Reviews community pull requests with focus on project quality.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/marvinli001/ClashMax?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~0 hours (45% approval). Keep your diff compact for rapid review.
Background / 背景 Batch delay testing is currently issued one node at a time, while the core has a whole-group endpoint /group/{name}/delay. MihomoAPIClient does not implement it yet. See roadmap item A6 (ROADMAP.md, 中文). 目前批量测速是逐节点打的，而内核有整组接口 /group/{name}/delay，MihomoAPIClient 还没实现。见路线图 A6。 Scope of this issue is the API client method and its tests only. Switching the batch-testing flow over to it is not part of this issue — see "Why the rewiring is out of scope" below. 本 issue 的范围只有 API 客户端方法及其测试。 把批量测速流程切换过去不属于本 issue——原因见下面"为什么切换不在范围内"。 Verified API contract / 已实测的接口约定 Probed against the bundled core (Resources/Core/mihomo, v1.19.29) using a select group holding one reachable node (DIRECT) and two dead nodes: 针对随包内核实测（v1.19.29），用一个含 1 个可达节点（DIRECT）和 2
Background / 背景 A stale fake-ip mapping currently can only be cleared by restarting the core. Mihomo exposes /cache/fakeip/flush for exactly this, and MihomoAPIClient does not implement it yet. See roadmap item A3 (ROADMAP.md, 中文). 目前 fake-ip 映射脏了只能靠重启内核清除。Mihomo 本来就有 /cache/fakeip/flush 这个接口，而 MihomoAPIClient 还没实现。见路线图 A3。 Scope of this issue is the API client method and its tests only. Surfacing it as a diagnosis fix action (the rest of A3) is deliberately not part of this issue. 本 issue 的范围只有 API 客户端方法及其测试。 把它做成诊断里的修复动作（A3 的其余部分）刻意不包含在内。 This is the smallest of the three API-client issues — a good one to pick if it is your first change here. 这是三个 API 客户端 issue 里最小的一个，如果是你在本仓库的第一次改动，推荐从这个开始。 Verified API contract / 已实测的接口约定 Probed
Background / 背景 MihomoAPIClient covers most of the Mihomo RESTful API, but /dns/query is missing. Without it the app can show rules and the exit IP, but not what DNS actually returned — a hole in the middle of the routing story. See roadmap item A2 (ROADMAP.md, 中文). MihomoAPIClient 已经覆盖了 Mihomo RESTful API 的大部分，但缺 /dns/query。缺了它，应用能展示规则和出口 IP，却展示不了 DNS 实际返回了什么。见路线图 A2。 Scope of this issue is the API client method and its tests only. The DNS panel UI described in A2 is deliberately not part of this issue. 本 issue 的范围只有 API 客户端方法及其测试。 A2 里描述的 DNS 面板 UI 刻意不包含在内。 Verified API contract / 已实测的接口约定 Probed against the bundled core (Resources/Core/mihomo, v1.19.29), so these are real responses, not guesses: 针对随包内核实测（v1.19.29），以下是真实返回，不是猜的： GET /dns/query?name=example.com&t
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to marvinli001/ClashMax, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of marvinli001/ClashMax acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
marvinli001/ClashMax has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 59.5 places marvinli001/ClashMax in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, marvinli001/ClashMax currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for marvinli001/ClashMax are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.