Grafeo is a pure-Rust, high-performance graph database that can be embedded as a library or run as a standalone database, with optional in-memory or persistent storage. Grafeo supports both LPG and RDF and all major query languages.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 20%
Response Time: -
First Timer Success: -
GrafeoDB/grafeo has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in GrafeoDB/grafeo respond to incoming external pull requests in approximately 0.0 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 51.1 places GrafeoDB/grafeo in the B tier.
The external contributor pull request merge rate for GrafeoDB/grafeo is 20.0%, based on public PR activity from non-core contributors.
GrafeoDB/grafeo currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Grafeo is a pure-Rust, high-performance graph database that can be embedded as a library or run as a standalone database, with optional in-memory or persistent storage. Grafeo supports both LPG and RDF and all major query languages.
Highly welcoming maintainers in GrafeoDB/grafeo. Prompt code reviews with positive guidance for new contributors.
Discussions in GrafeoDB/grafeo focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/GrafeoDB/grafeo?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (25% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Summary The compact-core store (#432) keeps cold chunks encoded and reads them in place, so a point read has to fetch one row from an encoded chunk. Bit-packed, bit-vector and dictionary data already do this in constant time with get(index). Two codecs cannot: RunLengthEncoding::get scans the runs from the start. DeltaBitPacked has no get; reading one value decodes the whole sequence. Proposal Run-length: binary search over cumulative run lengths. Delta: a sampled skip index (a reconstructed value every N entries), so one read adds at most N deltas. Keep the extra memory bounded and stated: build the index per cold chunk or make it opt-in, so bulk-decode users (adjacency chunks, CompactStore) don't pay for it. Any on-disk layout follows the chunk format from #449. Acceptance get(row) matches decode()[row] for every row: property tests on random data, plus empty, single run, first row, last row and out of range. A benchmark of a point read against a full decode at the planned chunk
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 GrafeoDB/grafeo, 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 GrafeoDB/grafeo acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 20.0% were successfully merged into the primary branch.
GrafeoDB/grafeo has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 51.1 places GrafeoDB/grafeo in the Solid tier.
The external pull request merge rate is 20.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, GrafeoDB/grafeo 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 GrafeoDB/grafeo 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.