A fast Golang Redis client that supports Client Side Caching, Auto Pipelining, RDMA, etc.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 83%
Response Time: 2d
First Timer Success: 80%
redis/rueidis has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in redis/rueidis respond to incoming external pull requests in approximately 45.2 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.5 places redis/rueidis in the A tier.
The external contributor pull request merge rate for redis/rueidis is 82.8%, based on public PR activity from non-core contributors.
redis/rueidis 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 redis/rueidis.
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/redis/rueidis?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~29 hours (96% approval). Large PRs (>500 lines) take ~217 hours (37% approval). Keep your diff compact for rapid review.
Context: We observed elevated Redis GET/SET failures that correlated strongly with increased DNS latency. Scaling up the CoreDNS pods reduced DNS latency. Subsequently, restarting the application service pods mitigated the Redis errors. While the temporal correlation is clear, the exact mechanism linking DNS latency to client side MOVED errors is not yet fully understood. One plausible explanation is that increased DNS latency caused Redis redirect handling to fail at the client. When a MOVED response was returned, DNS resolution or connection attempts to the redirected node may have exceeded client timeouts, causing the redirect to fail and the original MOVED error to surface. Repeated failures may have left clients with stale topology until service pods were restarted. Is the understanding here accurate? As a follow-up, whether any client-side settings such as retries on MOVED, redirect-specific timeouts, and topology refresh on failures can be tuned to enable self-healing from tran
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 redis/rueidis, 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 redis/rueidis acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.8% were successfully merged into the primary branch.
redis/rueidis has a recorded first-timer success rate of 80.0%. 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.5 places redis/rueidis in the Welcoming tier.
The external pull request merge rate is 82.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, redis/rueidis 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 redis/rueidis 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.