Fast and flexible physics-based battery models in Python
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 63%
Response Time: -
First Timer Success: 50%
pybamm-team/PyBaMM has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pybamm-team/PyBaMM 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 62.3 places pybamm-team/PyBaMM in the A tier.
The external contributor pull request merge rate for pybamm-team/PyBaMM is 62.9%, based on public PR activity from non-core contributors.
pybamm-team/PyBaMM currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in pybamm-team/PyBaMM. Maintains strict focus on technical quality and test standards.
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/pybamm-team/PyBaMM?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday 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 (79% approval). Large PRs (>500 lines) take ~115 hours (28% approval). Keep your diff compact for rapid review.
PyBaMM Version 25.12.2 Python Version 3.12 Describe the bug First of all, thank you for the great work on PyBaMM. I’d like to propose an improvement regarding how JAX availability is handled. Summary Currently, has_jax() in util.py only checks whether jax is installed, but not which version is installed. This can lead to unexpected import-time failures when an incompatible JAX version is present in the environment. If PyBaMM is installed with the pybamm[jax] extra, dependency resolvers (e.g., Poetry, etc.) correctly enforce the required JAX version constraints. However, when installing PyBaMM without the JAX extra, there is an assumption (both by users and dependency resolvers) that PyBaMM is completely independent of JAX. In practice, this is not entirely true. If JAX is already installed in the environment (e.g., via a transitive dependency from another library or as a direct dependency), PyBaMM may still attempt to call JAX functionality and break the existing codebase. Minimal Re
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 pybamm-team/PyBaMM, 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 pybamm-team/PyBaMM acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.9% were successfully merged into the primary branch.
pybamm-team/PyBaMM has a recorded first-timer success rate of 50.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 62.3 places pybamm-team/PyBaMM in the Welcoming tier.
The external pull request merge rate is 62.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pybamm-team/PyBaMM 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 pybamm-team/PyBaMM 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.