The CORE-V CVA6 is a highly configurable, 6-stage RISC-V core for both application and embedded applications. Application class configurations are capable of booting Linux.
C-Rank Grade: D (Risky) - 20/100
External PR Merge Rate: -
Response Time: 7d
First Timer Success: -
openhwfoundation/cva6 has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openhwfoundation/cva6 respond to incoming external pull requests in approximately 166.3 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 19.8 places openhwfoundation/cva6 in the D tier.
The external contributor pull request merge rate for openhwfoundation/cva6 is 0.0%, based on public PR activity from non-core contributors.
openhwfoundation/cva6 currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The CORE-V CVA6 is a highly configurable, 6-stage RISC-V core for both application and embedded applications. Application class configurations are capable of booting Linux.
Collaborative maintainer environment in openhwfoundation/cva6. Reviews community pull requests with focus on project quality.
Discussions in openhwfoundation/cva6 focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/openhwfoundation/cva6?utm_source=github&utm_medium=badge)
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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~108 hours (81% approval). Large PRs (>500 lines) take ~798 hours (29% approval). Keep your diff compact for rapid review.
Code of Conduct I have searched the existing bug issues. I am a human engaging in an interpersonal interaction. During this interaction, my words are my own and are not generated. If relevant, I provide links to my sources. CVA6 commit affected 6348e9e Bug Description In frontend, the prediction always_comb computes ras_push/ras_pop/ras_update as single scalars in a loop that runs the fetch slots high-index down to slot 0. The branch arm clears ras_push/ras_pop unconditionally, including when the branch is not taken. A not-taken branch falls through, so the upper slot behind it is on-path and consumed. Because slot 0 is processed last, its not-taken arm overwrites the push/pop the upper call/return just set. predict_address is unaffected and the redirect this cycle is correct. Only the RAS update is lost, so a dropped push mispredicts the eventual ret, and a dropped pop corrupts the next return. Reachable on any RVC config (INSTR_PER_FETCH = 2, e.g. cv32a6_imac_sv32). Buggy Code co
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 openhwfoundation/cva6, 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 openhwfoundation/cva6 acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
openhwfoundation/cva6 has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 19.8 places openhwfoundation/cva6 in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openhwfoundation/cva6 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 openhwfoundation/cva6 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.