Suite of tools containing an in-memory vector datastore and AI proxy
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 82%
Response Time: -
First Timer Success: 80%
deven96/ahnlich has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in deven96/ahnlich 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 68.8 places deven96/ahnlich in the A tier.
The external contributor pull request merge rate for deven96/ahnlich is 82.1%, based on public PR activity from non-core contributors.
deven96/ahnlich currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in deven96/ahnlich. 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/deven96/ahnlich?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (37% approval). Keep your diff compact for rapid review.
Should probably have a list endpoint that allows iterating through a store. We could provide support for predicate conditions as well which effectively gives us an operation like message ListStore { string store = 1; optional uint64 start_key = 2; // StoreKeyId perhaps as a token to start from uint32 limit = 3; // Max number of items to return optional PredicateCondition condition = 4; // Filter results by predicate optional string schema = 5; // Schema/namespace } Given that ordering has no semantic meaning, should we bother to implement ordering. If yes we could still sort by StoreKeyId first. Checklist follow up to this would be: Integrating endpoint into Ahnlich AI and CLI Updating libraries to include new endpoint Updating https://ahnlich.dev public docs VectorDBZ as #396 stated
We should probably have a codesandbox.io demo that allows folks to begin using ahnlich without any local setup
An MCP server that exposes Ahnlich as tools any MCP-compatible agent can discover and use (Claude Desktop, Cursor, VS Code Copilot, custom agents). Each tool maps to one Ahnlich operation. Agents compose these into workflows. Potential Use cases: Agent working memory: agent stores intermediate findings during multi-step tasks, searches them later. No pre-built pipeline needed. Local file organization: agent reads a user's Downloads folder with its own filesystem access, stores descriptions in Ahnlich through the MCP server, then searches semantically ("find that ML paper I downloaded last month"). Personal knowledge base: agent indexes notes and research as the user shares them. The store becomes searchable memory over time.
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 deven96/ahnlich, 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 deven96/ahnlich acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 82.1% were successfully merged into the primary branch.
deven96/ahnlich has a recorded first-timer success rate of 80.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 68.8 places deven96/ahnlich in the Welcoming tier.
The external pull request merge rate is 82.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, deven96/ahnlich 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 deven96/ahnlich 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.