Run any agent on any model, models stored as OCI images
C-Rank Grade: S (Elite) - 69/100
External PR Merge Rate: 58%
Response Time: -
First Timer Success: 63%
llmmanorg/llmman has a recorded first-timer success rate of 62.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in llmmanorg/llmman 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.3 places llmmanorg/llmman in the S tier.
The external contributor pull request merge rate for llmmanorg/llmman is 58.3%, based on public PR activity from non-core contributors.
llmmanorg/llmman currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in llmmanorg/llmman. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in llmmanorg/llmman 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/llmmanorg/llmman?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (73% approval). Large PRs (>500 lines) take ~115 hours (26% approval). Keep your diff compact for rapid review.
Models can be huge terabytes or greater. It is easy for models to fill up disks. Before pulling a model, check can the disk fit it before pulling. Might be worth seeing if there is prior art in docker/podman/llama.cpp/ollama.
llmman should provide an explicit, per-invocation way to supply a Hugging Face token (CLI flag + Web UI) so that baked models whose weights come from gated or private Hugging Face repositories can be pulled.
When I run llmman serve, the final line of the output tells me llmman serve listening on 127.0.0.1:17434 If you change that to llmman serve listening on http://127.0.0.1:17434 many terminal emulators, including the two I use most often on Linux, Konsole and ghostty, can treat it as an active link, and I can open it in the browser with `CTRL-mouse click.
So: llmman run hf.co/unsloth/Qwen-Image-2.1-GGUF "A manatee in a sunlit lagoon" just works.
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 llmmanorg/llmman, 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 llmmanorg/llmman acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 58.3% were successfully merged into the primary branch.
llmmanorg/llmman has a recorded first-timer success rate of 62.5%. Repositories ranked Elite 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.3 places llmmanorg/llmman in the Elite tier.
The external pull request merge rate is 58.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, llmmanorg/llmman currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for llmmanorg/llmman 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.