Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 64%
Response Time: 19h
First Timer Success: 50%
apache/kvrocks has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in apache/kvrocks respond to incoming external pull requests in approximately 19.1 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 60.0 places apache/kvrocks in the A tier.
The external contributor pull request merge rate for apache/kvrocks is 64.3%, based on public PR activity from non-core contributors.
apache/kvrocks currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in apache/kvrocks. 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/apache/kvrocks?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (80% approval). Large PRs (>500 lines) take ~92 hours (29% approval). Keep your diff compact for rapid review.
Search before asking I had searched in the issues and found no similar framework-level issue. I found issues about specific subcommands or documentation, but not one about making subcommands a first-class command abstraction. Motivation Kvrocks has many Redis-compatible command families whose behavior is selected by the second token, such as COMMAND GETKEYS, CONFIG GET/SET, CLIENT LIST/KILL, CLUSTER *, SCRIPT *, and NAMESPACE GET/SET/ADD/DEL/CURRENT. Currently, these subcommands are usually handled inside the root command implementation by manually parsing args_[1]. This makes subcommands second-class from the command framework's point of view: Subcommands cannot have their own registered metadata, such as arity, flags, key specs, and category. Command resolution, key extraction, command renaming, Lua command invocation, and command introspection have to reason about only the root command. Root command implementations tend to become large dispatchers instead of focused command hand
This thread collects open issues that are suitable for contributors who want to work on Apache Kvrocks. We very much welcome anyone to claim the tasks and start contributing to Kvrocks. If you need any help during the contribution process, you can leave a message under the corresponding issue. Good first issues High priority: #3517 #3128 #2302 #2628 #884 #755 #3552 Redis compatibility High priority: #3518 High priority: #3123 #3411 #3073 #2610 #2500 #2414 #2133 #3319 #3436 CI and reliability High priority: #3515 #3157 #3153 #3100 #1759 Cluster and replication #3498 #3496 #3495 #3147 #3113 #3095 #2473 #2177 Performance and optimization #3314 #2144 #2398 #2305 #2297
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 apache/kvrocks, 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 apache/kvrocks acknowledge new external contributions in approximately 19 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.3% were successfully merged into the primary branch.
apache/kvrocks has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~19 hours. 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 60.0 places apache/kvrocks in the Welcoming tier.
The external pull request merge rate is 64.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/kvrocks 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 apache/kvrocks 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.