Mac app and JSON CLI to monitor every Claude Code, Codex, Cursor Agent and Pi session on your machine. See which agent needs permission, which is working, and which is idle. Works with any terminal or IDE. Free, open source (MIT).
C-Rank Grade: B (Solid) - 55/100
External PR Merge Rate: 67%
Response Time: 16d
First Timer Success: 50%
minchenlee/c9watch has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in minchenlee/c9watch respond to incoming external pull requests in approximately 388.2 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 54.7 places minchenlee/c9watch in the B tier.
The external contributor pull request merge rate for minchenlee/c9watch is 66.7%, based on public PR activity from non-core contributors.
minchenlee/c9watch currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Mac app and JSON CLI to monitor every Claude Code, Codex, Cursor Agent and Pi session on your machine. See which agent needs permission, which is working, and which is idle. Works with any terminal or IDE. Free, open source (MIT).
Active maintainer team in minchenlee/c9watch 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/minchenlee/c9watch?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
Current State PR #6 added initial mobile web client support with basic responsive styles: flex-wrap on stats row and action buttons max-width / text-overflow constraints on badges and branch names Improvements Needed The current responsive behavior is functional but could be refined for a better mobile experience. Areas to consider: Optimize card layout for narrow screens Improve stats row presentation on mobile Refine action button sizing/spacing for touch targets Better handling of long branch names and project paths Typography and spacing adjustments for mobile readability Consider different layouts for portrait vs landscape orientations Context The initial implementation was done with systems software background (not frontend expertise), so there's room for UI/UX improvements from someone with stronger CSS/design skills. Related PR #6 - Initial mobile web client support
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 minchenlee/c9watch, 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 minchenlee/c9watch acknowledge new external contributions in approximately 16 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
minchenlee/c9watch has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 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 54.7 places minchenlee/c9watch in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, minchenlee/c9watch currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for minchenlee/c9watch 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.