Nornicdb is a distributed low-latency, Graph+Vector, Temporal MVCC with all sub-ms HNSW search, graph traversal, and writes. Using Neo4j Bolt/Cypher and qdrant's gRPC means you can switch with no changes while adding intelligent features like schemas, managed embeddings, reranking+llm, GPU accel, Auto-TLP, Policy-based Memory Decay, and MCP server.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 55%
Response Time: -
First Timer Success: 50%
orneryd/NornicDB 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 orneryd/NornicDB 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 69.4 places orneryd/NornicDB in the A tier.
The external contributor pull request merge rate for orneryd/NornicDB is 54.9%, based on public PR activity from non-core contributors.
orneryd/NornicDB currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Nornicdb is a distributed low-latency, Graph+Vector, Temporal MVCC with all sub-ms HNSW search, graph traversal, and writes. Using Neo4j Bolt/Cypher and qdrant's gRPC means you can switch with no changes while adding intelligent features like schemas, managed embeddings, reranking+llm, GPU accel, Auto-TLP, Policy-based Memory Decay, and MCP server.
Balanced & professional review environment in orneryd/NornicDB. 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/orneryd/NornicDB?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (69% approval). Large PRs (>500 lines) take ~115 hours (25% approval). Keep your diff compact for rapid review.
I feel like I am not the best at UI design, while I understand UX this also has a large API surface and I am more focued on internals, API correctness, and performance than I am at UI elements at the moment. This would be a great first issue for anyone who is a UI expert that wants to overhaul the UI with something ✨amazing✨ to be in line with the features and provide a cleaner UX. even if you want to rewrite it in a different framework and overhaul the whole architecture, have at it. If this takes off before I can get to the UI myself, the community can even vote on/combine the ideas people have. https://github.com/orneryd/NornicDB/blob/main/docs/plans/ui-enhancements.md Thanks for all of your support 🙏
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 orneryd/NornicDB, 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 orneryd/NornicDB acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.9% were successfully merged into the primary branch.
orneryd/NornicDB 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 ~-. 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 69.4 places orneryd/NornicDB in the Welcoming tier.
The external pull request merge rate is 54.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, orneryd/NornicDB 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 orneryd/NornicDB 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.