CS infrastructure components for HPC applications
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 71%
Response Time: 14h
First Timer Success: 60%
llnl/axom 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 llnl/axom respond to incoming external pull requests in approximately 14.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 66.4 places llnl/axom in the A tier.
The external contributor pull request merge rate for llnl/axom is 71.3%, based on public PR activity from non-core contributors.
llnl/axom currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in llnl/axom. Prompt code reviews with positive guidance for new contributors.
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/llnl/axom?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (89% approval). Large PRs (>500 lines) take ~68 hours (32% approval). Keep your diff compact for rapid review.
I asked Claude to review all issues in the Axom GitHub repo and to generate a report on which issues are fixed and could be closed, which are outdated, and which should be high priority, etc. Here's what it did. Hopefully, we can use this to do some house cleaning and planning. We did something similar in RAJA (thanks @davidbeckingsale ) and we were able to close over 40 issues in short order. Note that I basically cut-and-pasted the report Claude generated. This needs some work to refine. Anyway, it's a start. If folks have thoughts/ideas about doing a more useful analysis on this, please share in a comment Axom GitHub Issues Analysis Report Generated: September 3, 2026 Total Issues Analyzed: 102 (PRs excluded) Executive Summary This report analyzes all open issues in the Axom GitHub repository. Issues have been categorized into three main groups: High Priority Issues (2): Active bugs, user requests, or recent enhancements requiring immediate attention Outdated/Inactive Issues (80
Exploring some code changes on a branch in Axom, I'm seeing compiler warnings that implicitly capturing this in a lambda expression is deprecated in C++20. Specifically, we are using the macros defined here in the code: https://github.com/llnl/axom/blob/develop/src/axom/core/Macros.hpp#L78 The warnings don't show up in Axom develop currently, but I expect that Axom developers and users will also run into these warnings at some point. In C++20, [=, this] is valid and well-formed (prior to C++20, it was either redundant or not considered valid depending on the compiler). However, this only works when a lambda expression is used within a class/struct member function. To avoid confusing inconsistent syntax, having multiple lamda macros for different code use cases, or macros that don't do anything, my suggestion would be to remove the AXOM_*_LAMBDA macros and make the capture syntax required. Currently, we have [=] in all the macros. FWIW, I don't see the reason for having capture-by-value
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 llnl/axom, 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 llnl/axom acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.3% were successfully merged into the primary branch.
llnl/axom 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 ~14 hours. 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 66.4 places llnl/axom in the Welcoming tier.
The external pull request merge rate is 71.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, llnl/axom 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 llnl/axom 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.