The official repository for the AiiDA code
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 64%
Response Time: 1d
First Timer Success: 40%
aiidateam/aiida-core has a recorded first-timer success rate of 40.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in aiidateam/aiida-core respond to incoming external pull requests in approximately 26.5 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 63.1 places aiidateam/aiida-core in the A tier.
The external contributor pull request merge rate for aiidateam/aiida-core is 64.0%, based on public PR activity from non-core contributors.
aiidateam/aiida-core 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 aiidateam/aiida-core. 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/aiidateam/aiida-core?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (80% approval). Large PRs (>500 lines) take ~127 hours (29% approval). Keep your diff compact for rapid review.
The introductory tutorial has been rewritten as a hands-on Gray-Scott reaction-diffusion example (Modules 0–3b). It can be found here: https://aiida.readthedocs.io/projects/aiida-core/en/support-v3-tutorial/ at the dedicated support-v3-tutorial branch, as we are breaking backwards compatibility on main towards a v3 release. This issue is the single place to collect feedback and track follow-ups for it, please comment here rather than opening separate issues, so everything stays in one thread. Worked through it and something was unclear, broken, or could be smoother? Drop a comment below, all feedback is welcome. Known follow-ups (will grow as suggestions come in; also linked here): Advanced modules 4–7 (remote HPC submission, querying at scale, conditional/adaptive workflows, error handling), currently "coming soon" placeholders. Publish the downloadable-notebook polishing Sphinx extension (docs/source/_ext/polish_download_notebooks.py) as a standalone, reusable extension for th
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 aiidateam/aiida-core, 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 aiidateam/aiida-core acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.0% were successfully merged into the primary branch.
aiidateam/aiida-core has a recorded first-timer success rate of 40.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 63.1 places aiidateam/aiida-core in the Welcoming tier.
The external pull request merge rate is 64.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, aiidateam/aiida-core 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 aiidateam/aiida-core 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.