P4_16 reference compiler
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 83%
Response Time: 22h
First Timer Success: 89%
p4lang/p4c has a recorded first-timer success rate of 88.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in p4lang/p4c respond to incoming external pull requests in approximately 21.9 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.7 places p4lang/p4c in the A tier.
The external contributor pull request merge rate for p4lang/p4c is 82.7%, based on public PR activity from non-core contributors.
p4lang/p4c currently has 1 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/p4lang/p4c?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.
This will make it convenient for other Bazel projects to depend on p4c. Without this, every Bazel project transitively depending on p4c has to specify a git_override for p4runtime, which is inconvenient and not compositional. I created the same issue for p4runtime and p4-constraints: p4lang/p4runtime#572 p4lang/p4-constraints#179
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 p4lang/p4c, 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 p4lang/p4c acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.7% were successfully merged into the primary branch.
p4lang/p4c has a recorded first-timer success rate of 88.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 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 63.7 places p4lang/p4c in the Welcoming tier.
The external pull request merge rate is 82.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, p4lang/p4c 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 p4lang/p4c 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.