AI Agent-first JS 逆向 MCP Server：有头 Chrome 调试、断点、网络/WebSocket 分析、Patchright 反检测，可选 CloakBrowser。
C-Rank Grade: D (Risky) - 13/100
External PR Merge Rate: -
Response Time: 11d
First Timer Success: -
zhizhuodemao/js-reverse-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zhizhuodemao/js-reverse-mcp respond to incoming external pull requests in approximately 259.8 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 13.0 places zhizhuodemao/js-reverse-mcp in the D tier.
The external contributor pull request merge rate for zhizhuodemao/js-reverse-mcp is 0.0%, based on public PR activity from non-core contributors.
zhizhuodemao/js-reverse-mcp does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
AI Agent-first JS 逆向 MCP Server：有头 Chrome 调试、断点、网络/WebSocket 分析、Patchright 反检测，可选 CloakBrowser。
Active maintainer team in zhizhuodemao/js-reverse-mcp welcoming community pull requests and bug fixes.
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/zhizhuodemao/js-reverse-mcp?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~169 hours (81% approval). Large PRs (>500 lines) take ~1247 hours (29% approval). Keep your diff compact for rapid review.
No cached good first issues currently tracked for zhizhuodemao/js-reverse-mcp.
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 zhizhuodemao/js-reverse-mcp, 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 zhizhuodemao/js-reverse-mcp acknowledge new external contributions in approximately 10 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
zhizhuodemao/js-reverse-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 days+. 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 13.0 places zhizhuodemao/js-reverse-mcp in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
zhizhuodemao/js-reverse-mcp does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for zhizhuodemao/js-reverse-mcp 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.