Track emissions from Compute and recommend ways to reduce their impact on the environment.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 48%
Response Time: -
First Timer Success: 60%
mlco2/codecarbon has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mlco2/codecarbon respond to incoming external pull requests in approximately 0.0 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 65.8 places mlco2/codecarbon in the A tier.
The external contributor pull request merge rate for mlco2/codecarbon is 47.9%, based on public PR activity from non-core contributors.
mlco2/codecarbon currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (100% positive review sentiment). Active code reviews with constructive guidance for new contributors in mlco2/codecarbon.
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/mlco2/codecarbon?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (60% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Where does the documentation need improvement? README.md What needs to be changed? The screen shots are from the old version of the dashboard.
Where does the documentation need improvement? At the end of the README.md we have a bibtex citation, but for the old v2.4.1 What needs to be changed? It will be nice to have an bibtex for v3.3.1 or even better, build it automatically. Additional context Viewed in https://www.cambridge.org/engage/coe/article-details/6aa98aa9d1922e37d55c3e1b that link to v2.4.1 instead of last version. Bonus See if we can force @sashavor into this list as she is a co-autor and made great contributions to CodeCarbon outside the code.
Is your feature request related to a problem? Please describe. When I run codecarbon monitor --help I only see: ╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────╮ │ --measure-power-secs <int> Interval between two measures. [default: 10] │ │ --api-call-interval <int> Number of measures between API calls. [default: 30] │ │ --api --no-api Choose to call Code Carbon API or not [default: api] │ │ --offline --no-offline Run in offline mode [default: no-offline] │ │ --country-iso-code <str> 3-letter country ISO code for offline mode │ │ --region
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 mlco2/codecarbon, 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 mlco2/codecarbon acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.9% were successfully merged into the primary branch.
mlco2/codecarbon has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 65.8 places mlco2/codecarbon in the Welcoming tier.
The external pull request merge rate is 47.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mlco2/codecarbon 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 mlco2/codecarbon 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.