Hive Console is part of the Hive GraphQL platform. Schema registry and analytics for GraphQL federation and other GraphQL APIs
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 74%
Response Time: 3d
First Timer Success: 77%
graphql-hive/console has a recorded first-timer success rate of 76.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in graphql-hive/console respond to incoming external pull requests in approximately 73.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 67.3 places graphql-hive/console in the A tier.
The external contributor pull request merge rate for graphql-hive/console is 74.1%, based on public PR activity from non-core contributors.
graphql-hive/console currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Hive Console is part of the Hive GraphQL platform. Schema registry and analytics for GraphQL federation and other GraphQL APIs
Collaborative maintainer environment in graphql-hive/console. Reviews community pull requests with focus on project quality.
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/graphql-hive/console?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~48 hours (93% approval). Large PRs (>500 lines) take ~353 hours (33% approval). Keep your diff compact for rapid review.
The only reference for deploying the CDN handler is right now our pulumi deployment config. There is several things we can improve there: Have archives for the CF worker and AWS Lambda with the corresponding code artifacts on the releases (e.g. https://github.com/graphql-hive/console/releases/tag/hive%409.4.1) Have instructions on how to deploy/configure the providers for a deployment of the code artifacts
Hi team, we are very happy to use a self hosted hive console for our graphql. Some weeks ago, we changed our domain from https://graphql-hive-dataservicelayer-prod.prod.zzzzzzz.aa.bbbbbb.cccc/xxxxxx something like https://graphql-hive-dataservicelayer-prod.proddsl.zzzzzzz.aa.bbbbbb.cccc/xxxxxx (I need to mask the real domain because of sensitive data, but the length of the domain and subdomains is correct) When I now invite colleagues, the invitation link is correctly generated https://graphql-hive-dataservicelayer-prod.proddsl.zzzzzzz.aa.bbbbbb.cccc/join/3f6f16d1c but in the email the dot between proddsl and zzzzzzz is missing and it looks like https://graphql-hive-dataservicelayer-prod.proddslzzzzzzz.aa.bbbbbb.cccc/join/3f6f16d1c I looked at the logs of the email component and the line breaks in the logs are exactly at this place, so maybe this is related to the missing dot in the email href=3D"https://graphql-hive-dataservicelayer-prod.proddsl= .zzzzzzz.aa.bbbbbb.
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 graphql-hive/console, 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 graphql-hive/console acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.1% were successfully merged into the primary branch.
graphql-hive/console has a recorded first-timer success rate of 76.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 67.3 places graphql-hive/console in the Welcoming tier.
The external pull request merge rate is 74.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, graphql-hive/console currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for graphql-hive/console 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.