Privacy-first LLM proxy and AI gateway - load balancing, multi-provider routing, API key management, usage tracking, rate limiting. Self-hosted. Zero knowledge of your prompts.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 50%
Response Time: -
First Timer Success: 100%
voidmind-io/voidllm has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in voidmind-io/voidllm 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 49.0 places voidmind-io/voidllm in the B tier.
The external contributor pull request merge rate for voidmind-io/voidllm is 50.0%, based on public PR activity from non-core contributors.
voidmind-io/voidllm currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in voidmind-io/voidllm. Reviews community pull requests with focus on project quality.
Discussions in voidmind-io/voidllm 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/voidmind-io/voidllm?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 23:00 to 03:00 UTC (23:00 - 03:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (62% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Problem / Motivation OpenSSF Scorecard flags this project as not fuzzed (Fuzzing check, score 0). More importantly, the parsing code on the proxy hot path has a track record of input-shape bugs: several defects in SSE event framing and in streaming PII restoration have been found through manual review rather than through tests. These are exactly the class of bugs that fuzzing finds cheaply and continuously, before they ship. Proposed Solution Add Go native fuzz targets (testing.F / FuzzXxx) for the parsers that handle untrusted or upstream-controlled input, each asserting a clear invariant rather than just "does not panic": SSE line/event parsing in the proxy streaming path (internal/proxy streaming response handling) — feed arbitrary byte streams as if from an upstream provider. Assert the forwarder never panics, never emits a partial SSE event, and that for well-formed input the bytes forwarded to the client equal the bytes received from upstream. The PII streaming restorer (in
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 voidmind-io/voidllm, 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 voidmind-io/voidllm acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
voidmind-io/voidllm has a recorded first-timer success rate of 100.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 49.0 places voidmind-io/voidllm in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, voidmind-io/voidllm 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 voidmind-io/voidllm 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.