Stateless Postgres Query Router.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 81%
Response Time: 7d
First Timer Success: 71%
pg-sharding/spqr has a recorded first-timer success rate of 71.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pg-sharding/spqr respond to incoming external pull requests in approximately 179.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 66.2 places pg-sharding/spqr in the A tier.
The external contributor pull request merge rate for pg-sharding/spqr is 80.9%, based on public PR activity from non-core contributors.
pg-sharding/spqr currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in pg-sharding/spqr. Reviews pull requests with focus on project architectural goals.
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/pg-sharding/spqr?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~117 hours (96% approval). Large PRs (>500 lines) take ~861 hours (36% approval). Keep your diff compact for rapid review.
PostgreSQL does not attach HINT to most errors; SPQR now does (since #3024). To stay closer to vanilla PostgreSQL behavior, add a router config flag that suppresses hints sent to clients: show_hints: true When false, strip the Hint field from pgproto3.ErrorResponse before sending to the client (keep it in SPQR logs). Related: #1966, #3024
Current: ERROR: rpc error: code = Unknown desc = shard "shard2" not found Proposed: ERROR: Shard "shard2" not found. Available shards: shard1 Hint: Run 'SHOW SHARDS' to see all configured shards. Run 'ADD SHARD shard2 WITH HOSTS ...' to create it. Related to: #1887
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 pg-sharding/spqr, 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 pg-sharding/spqr acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.9% were successfully merged into the primary branch.
pg-sharding/spqr has a recorded first-timer success rate of 71.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 66.2 places pg-sharding/spqr in the Welcoming tier.
The external pull request merge rate is 80.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pg-sharding/spqr 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 pg-sharding/spqr 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.