NGINX Gateway Fabric provides an implementation for the Gateway API using NGINX as the data plane.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 87%
Response Time: 4d
First Timer Success: 94%
nginx/nginx-gateway-fabric has a recorded first-timer success rate of 93.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nginx/nginx-gateway-fabric respond to incoming external pull requests in approximately 105.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.2 places nginx/nginx-gateway-fabric in the A tier.
The external contributor pull request merge rate for nginx/nginx-gateway-fabric is 87.1%, based on public PR activity from non-core contributors.
nginx/nginx-gateway-fabric currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in nginx/nginx-gateway-fabric. 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/nginx/nginx-gateway-fabric?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~69 hours (96% approval). Large PRs (>500 lines) take ~506 hours (39% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
Go bindings for Ceph :octopus: :octopus: :octopus:
A distributed, proof of stake blockchain designed for the financial services industry.
🛡️ Synchronize AdGuard Home config to replicas
NGINX Docs recently changed their headers to include the following fields: f5-keywords, f5-description, f5-summary, which many of our existing docs do not contain. I think these fields help with search results + AI metadata gathering for when they collect information. We should update our documents to contain these metadata fields. Additionally, many of our titles could be more descriptive. Titles such as "ListenerSet API, UDPRoute, TCPRoute, Rate Limit Policy API..." and more could be expanded upon to better tell the user what the guide is about.
gocyclo exceptions are in a few spots in the code base, most of which are just temporary satisfactions for the linter. We should refactor these functions so the logic complexity gocyclo checks for is smaller, increasing understandability and readability for developers.
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 nginx/nginx-gateway-fabric, 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 nginx/nginx-gateway-fabric acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.1% were successfully merged into the primary branch.
nginx/nginx-gateway-fabric has a recorded first-timer success rate of 93.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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.2 places nginx/nginx-gateway-fabric in the Welcoming tier.
The external pull request merge rate is 87.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nginx/nginx-gateway-fabric 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 nginx/nginx-gateway-fabric 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.