Universal LLM API client — 163 providers, 14 native language bindings, powered by a Rust core
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 72%
Response Time: -
First Timer Success: 75%
xberg-io/liter-llm has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in xberg-io/liter-llm 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 58.6 places xberg-io/liter-llm in the A tier.
The external contributor pull request merge rate for xberg-io/liter-llm is 72.2%, based on public PR activity from non-core contributors.
xberg-io/liter-llm does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in xberg-io/liter-llm. 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/xberg-io/liter-llm?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (90% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
task test-apps:smoke:rust currently runs cargo run in test_apps/rust, whose sole binary is the generated mock-server. It does not run tests/smoke_test.rs and can wait for stdin instead of verifying the published library. task test-apps:smoke:go runs go test -v -run "Test_Smoke", but test_apps/go/smoke_test.go contains names such as Test_AnthropicChat and Test_AzureChat; the filter matches none of those smoke tests. Align these legacy commands with generated test names or delegate to the canonical alef test-apps run --lang rust,go registry consumer runner, with regression coverage that rejects zero executed tests. Release verification uses the canonical runner rather than these two legacy tasks.
poly lint is green in this repo, but not because the code is under the size and complexity limits. The offenders are listed individually in alef.toml under the # --- quality-debt baseline --- block. Refreshed 2026-09-30 against v2.1.2 (d03342788). Counts and paths below are read directly from the alef.toml baseline block, not from the original list. Why it is a per-file list and not a rule switched off Listing each file keeps the metrics active on every file that is not listed, so new code is still checked and new violations still fail. The cost is that each existing offender has to be paid off individually — which is exactly what makes each one a self-contained task. Current status 44 findings across 36 files remain (down from 71 across 45; file-too-long 20, function-too-long 20, cyclomatic-complexity 3, too-many-parameters 1). Cleared by #235–#243 (entries deleted from the baseline): crates/liter-llm/src/tower/budget.rs crates/liter-llm/src/http/streaming.rs crates/liter-ll
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 xberg-io/liter-llm, 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 xberg-io/liter-llm acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.2% were successfully merged into the primary branch.
xberg-io/liter-llm has a recorded first-timer success rate of 75.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 58.6 places xberg-io/liter-llm in the Welcoming tier.
The external pull request merge rate is 72.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
xberg-io/liter-llm does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for xberg-io/liter-llm 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.