Open-source Apple Silicon system monitor for macOS.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 18%
Response Time: 9d
First Timer Success: -
offyotto/Core-Monitor has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in offyotto/Core-Monitor respond to incoming external pull requests in approximately 225.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 46.2 places offyotto/Core-Monitor in the B tier.
The external contributor pull request merge rate for offyotto/Core-Monitor is 18.2%, based on public PR activity from non-core contributors.
offyotto/Core-Monitor currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in offyotto/Core-Monitor. Reviews community pull requests with focus on project quality.
Discussions in offyotto/Core-Monitor focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/offyotto/Core-Monitor?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~146 hours (23% approval). Large PRs (>500 lines) take ~1081 hours (15% approval). Keep your diff compact for rapid review.
Who this is for: Anyone with an M1 BASE (With fan) or M1 Max Mac. No coding required. What I need tested: Install the latest Core-Monitor direct build. Confirm temperature sensors populate, fan RPM is detected correctly, System mode behaves normally, and verify manual fan control can be enabled and returned to System control. Please comment with: Mac model, chip, macOS version, fan count, whether temperatures appear correctly, whether RPM appears correctly, and any screenshots/errors. No code contribution required. A test result in this issue is already useful. If the model needs a mapping/code fix afterward, we can turn that into a separate PR. M1 Pro has ALREADY been tested.
Who this is for: Anyone with an M2 Pro or M2 Max Mac. No coding required. What I need tested: Install the latest Core-Monitor direct build. Confirm temperature sensors populate, fan RPM is detected correctly, System mode behaves normally, and verify manual fan control can be enabled and returned to System control. Please comment with: Mac model, chip, macOS version, fan count, whether temperatures appear correctly, whether RPM appears correctly, and any screenshots/errors. No code contribution required. A test result in this issue is already useful. If the model needs a mapping/code fix afterward, we can turn that into a separate PR. IF you have a base M2, it is ALREADY tested.
Test Fan control and Temp sensors on M4 generation
Test Fan Control and Temp Sensors on Apple M3 (Pro, Max, Ultra, Base) Who this is for: Anyone with an M3 Generation Mac (with fans). No coding required. What I need tested: Install the latest Core-Monitor direct build. Confirm temperature sensors populate, fan RPM is detected correctly, System mode behaves normally, and verify manual fan control can be enabled and returned to System control. Please comment with: Mac model, chip, macOS version, fan count, whether temperatures appear correctly, whether RPM appears correctly, and any screenshots/errors. No code contribution required. A test result in this issue is already useful. If the model needs a mapping/code fix afterward, we can turn that into a separate PR.
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 offyotto/Core-Monitor, 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 offyotto/Core-Monitor acknowledge new external contributions in approximately 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 18.2% were successfully merged into the primary branch.
offyotto/Core-Monitor has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 46.2 places offyotto/Core-Monitor in the Solid tier.
The external pull request merge rate is 18.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, offyotto/Core-Monitor currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for offyotto/Core-Monitor 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.