LadybugDB a graph database
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 81%
Response Time: 13h
First Timer Success: 77%
LadybugDB/ladybug has a recorded first-timer success rate of 76.9%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in LadybugDB/ladybug respond to incoming external pull requests in approximately 13.3 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 71.0 places LadybugDB/ladybug in the S tier.
The external contributor pull request merge rate for LadybugDB/ladybug is 81.2%, based on public PR activity from non-core contributors.
LadybugDB/ladybug currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in LadybugDB/ladybug. 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/LadybugDB/ladybug?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (96% approval). Large PRs (>500 lines) take ~64 hours (37% approval). Keep your diff compact for rapid review.
Motivation LogicalOperatorUtils::logicalOperatorTypeToString() threw Unknown logical operator type. at runtime on LSQB q9: the recent COUNT_ANTI_EDGE_CHAIN operator was added to the enum but a case was never added to the type-to-string switch. -Wall -Wextra (which includes -Wswitch) would have caught this at compile time — but the switch ended in default: throw RuntimeException(...), and any default: label silences -Wswitch. The failure mode was converted from a build error into a runtime crash. The same bug class exists in the sibling enum→string switches listed below. This was fixed for logicalOperatorTypeToString (see commit adding COUNT_ANTI_EDGE_CHAIN); this issue tracks applying the pattern to the rest. The pattern For switches that are exhaustive in intent (every enumerator returns / is handled): // Before: -Wswitch silently disabled switch (type) { case Foo::A: return "A"; default: throw RuntimeException("Unknown type."); } // After: -Wswitch enforces coverage; missing enu
We have nightly sanitizer runs now. These are beginner friendly tasks to fix https://github.com/LadybugDB/ladybug/actions/runs/33396106462/job/99500889127
API C++ Description Similar in concept: https://github.com/duckdb/extension-template Instead of stuffing everything into https://github.com/LadybugDB/extensions, this allows people to maintain their own unofficial extensions.
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 LadybugDB/ladybug, 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 LadybugDB/ladybug acknowledge new external contributions in approximately 13 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.2% were successfully merged into the primary branch.
LadybugDB/ladybug has a recorded first-timer success rate of 76.9%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 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 71.0 places LadybugDB/ladybug in the Elite tier.
The external pull request merge rate is 81.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, LadybugDB/ladybug 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 LadybugDB/ladybug 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.