gRPC to JSON proxy generator following the gRPC HTTP spec
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 69%
Response Time: 1d
First Timer Success: 43%
grpc-ecosystem/grpc-gateway has a recorded first-timer success rate of 42.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in grpc-ecosystem/grpc-gateway respond to incoming external pull requests in approximately 34.6 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 57.0 places grpc-ecosystem/grpc-gateway in the A tier.
The external contributor pull request merge rate for grpc-ecosystem/grpc-gateway is 68.5%, based on public PR activity from non-core contributors.
grpc-ecosystem/grpc-gateway currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (77% critical review signals). Ensure PRs strictly follow guidelines before requesting review in grpc-ecosystem/grpc-gateway.
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/grpc-ecosystem/grpc-gateway?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~22 hours (86% approval). Large PRs (>500 lines) take ~166 hours (31% approval). Keep your diff compact for rapid review.
🐛 Bug Report We recently had a very serious CVE in our project https://docs.velociraptor.app/announcements/advisories/cve-2026-18972/ due to the default header matcher in grpc gateway. The default header matcher copies all HTTP headers into the grpc metadata without filtering, allowing arbitrary metadata items to be added unexpectedly. If the user of grpc gateway does not set a specific header matcher with runtime.WithIncomingHeaderMatcher() option this can pollute the metadata with unexpected values injected by the http header. I think a better more secure design is a noop header matcher which requires deliberately accepting some headers to be forwarded to the metadata. (i.e. opt in rather than opt out). If the user is trying to capture specific headers then they should declare those specific headers to be injected into the grpc metadata. To Reproduce The default runtime.NewServeMux( ) installs a default header matcher which copies all headers to the grpc metadata. Expected behavi
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 grpc-ecosystem/grpc-gateway, 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 grpc-ecosystem/grpc-gateway acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.5% were successfully merged into the primary branch.
grpc-ecosystem/grpc-gateway has a recorded first-timer success rate of 42.9%. 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 57.0 places grpc-ecosystem/grpc-gateway in the Welcoming tier.
The external pull request merge rate is 68.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, grpc-ecosystem/grpc-gateway 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 grpc-ecosystem/grpc-gateway 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.