RamaLama is an open-source developer tool that simplifies the local serving of AI models from any source and facilitates their use for inference in production, all through the familiar language of containers.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 44%
Response Time: <1h
First Timer Success: 33%
containers/ramalama has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in containers/ramalama respond to incoming external pull requests in approximately 1.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 57.8 places containers/ramalama in the A tier.
The external contributor pull request merge rate for containers/ramalama is 44.4%, based on public PR activity from non-core contributors.
containers/ramalama currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in containers/ramalama. Reviews pull requests with focus on project architectural goals.
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/containers/ramalama?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (56% approval). Large PRs (>500 lines) take ~5 hours (20% approval). Keep your diff compact for rapid review.
Issue Description The docs describes new line continuation characters as just \, however, in practice chat actually requires a space followed by \. This comes from this implementation in chat.py self.content.append(user_content.rstrip(" \\")) Steps to reproduce the issue run a model Begin typing a message with a continuation line. e.g. "hello\ how are you?" Describe the results you received The new line character submits the message rather than continuing. Describe the results you expected A multiline message. ramalama info output { "Accelerator": "none", "Config": { "api_key": "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", "carimage": "quay.io/ramalama/ramalama", "engine": "docker", "settings": { "config_files": [ "/Users/ieaves/.config/ramalama/ramalama.conf" ] },
Issue Description llama-server /models api returns a 503 error while the model is loading. ramalama run handles this but ramalama chat currently does not. For interactive use this isn't a major issue but it would be good to fix this. Worked around this for CI in #2342 Steps to reproduce the issue Run ramalama chat soon after ramalama serve --detach Describe the results you received ramalama chat fails Describe the results you expected ramalama chat succeeds ramalama info output N/A Upstream Latest Release Yes Additional environment details No response Additional information No response
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 containers/ramalama, 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 containers/ramalama acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 44.4% were successfully merged into the primary branch.
containers/ramalama has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 57.8 places containers/ramalama in the Welcoming tier.
The external pull request merge rate is 44.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, containers/ramalama currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for containers/ramalama 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.