A modern replacement for Redis and Memcached
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 79%
Response Time: 2d
First Timer Success: 64%
dragonflydb/dragonfly has a recorded first-timer success rate of 63.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dragonflydb/dragonfly respond to incoming external pull requests in approximately 45.9 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 64.8 places dragonflydb/dragonfly in the A tier.
The external contributor pull request merge rate for dragonflydb/dragonfly is 78.9%, based on public PR activity from non-core contributors.
dragonflydb/dragonfly currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in dragonflydb/dragonfly. Maintains strict focus on technical quality and test standards.
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/dragonflydb/dragonfly?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 ~30 hours (96% approval). Large PRs (>500 lines) take ~220 hours (35% approval). Keep your diff compact for rapid review.
Implement client trackinginfo subcommand. Dragonfly already supports client command but misses trackinginfo. Command: https://valkey.io/commands/client-tracking/ And trackinginfo https://valkey.io/commands/client-trackinginfo/ @miledxz PTAL
Currently following is required to make Dragonfly operator work IPv6 only or dual stacked environments: args: - "--bind=::" - "--admin_bind=::" As the day of CONFIG_IPV4=n is getting closer by every day I would suggest switching listening from 0.0.0.0 to :: in Dragonfly binary itself This is compatible with all modes IPv4-only, IPv6-only and dual stack
Describe the bug Python App with redisvl 0.26.0 Server redis_version:7.4.0 dragonfly_version:df-i1.40.6 Ran across this new issue when I attached my Agentic Harness to a cloud instance today... Part of the logic executed does FT.INFO against the available indexes and if not found, creates the index. This flow failed because the error message from a missing index returned by dragonfly didn't contain the expected text. redisvl's exists() check swallows "missing index" errors by matching known error-message wordings, but Dragonfly phrases it as "Index with name 'X' not found" — none of redisvl's known fragments ("unknown index name", "no such index", "search_index_not_found", "index not found") match that ordering, so the error propagates as fatal instead of being treated as "index doesn't exist yet, create it." Claude fixed it in my app code by adding wording to the listed matches for the exception message: # redisvl.exists() treats FT.INFO failures as "index missing" only if the error
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 dragonflydb/dragonfly, 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 dragonflydb/dragonfly acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.9% were successfully merged into the primary branch.
dragonflydb/dragonfly has a recorded first-timer success rate of 63.6%. 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 64.8 places dragonflydb/dragonfly in the Welcoming tier.
The external pull request merge rate is 78.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dragonflydb/dragonfly 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 dragonflydb/dragonfly 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.