clad -- automatic differentiation for C/C++
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 61%
Response Time: 1d
First Timer Success: 53%
vgvassilev/clad has a recorded first-timer success rate of 52.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vgvassilev/clad respond to incoming external pull requests in approximately 34.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 55.7 places vgvassilev/clad in the A tier.
The external contributor pull request merge rate for vgvassilev/clad is 61.1%, based on public PR activity from non-core contributors.
vgvassilev/clad currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/vgvassilev/clad?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Here the valgrind builds fail on llvm21 because there are some outstanding valgrind issues we need to fix in clad's codebase.
The current benchmarks after we moved to release builds yield 0ns which likely means the optimizer optimized some codes out. That needs to be fixed and we will need more benchmarks to make sure we have a good coverage.
When running benchmarks clad changes the compiler with the compiler it was built against in: clad/CMakeLists.txt Lines 329 to 352 in 44d4794 set(stored_cxx_compiler ${CMAKE_CXX_COMPILER}) set(stored_cxx_flags ${CMAKE_CXX_FLAGS}) set(CMAKE_CXX_COMPILER ${LLVM_TOOLS_BINARY_DIR}/clang) # Filter some unsupported flags by clang. string(REPLACE "-fno-lifetime-dse" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}") string(REPLACE "-Wno-class-memaccess" "" CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}") endif() if (NOT CL
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 vgvassilev/clad, 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 vgvassilev/clad acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.1% were successfully merged into the primary branch.
vgvassilev/clad has a recorded first-timer success rate of 52.6%. 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 55.7 places vgvassilev/clad in the Welcoming tier.
The external pull request merge rate is 61.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vgvassilev/clad 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 vgvassilev/clad 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.