Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 9%
Response Time: 21h
First Timer Success: 50%
litmuschaos/litmus has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in litmuschaos/litmus respond to incoming external pull requests in approximately 20.6 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 52.1 places litmuschaos/litmus in the B tier.
The external contributor pull request merge rate for litmuschaos/litmus is 9.1%, based on public PR activity from non-core contributors.
litmuschaos/litmus currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
Highly welcoming maintainers in litmuschaos/litmus. Prompt code reviews with positive guidance for new contributors.
Discussions in litmuschaos/litmus 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/litmuschaos/litmus?utm_source=github&utm_medium=badge)
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 Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (11% approval). Large PRs (>500 lines) take ~99 hours (15% approval). Keep your diff compact for rapid review.
I couldn’t find any official documentation for installing LitmusChaos without deploying the ChaosCenter (UI). My goal is to run LitmusChaos purely as infrastructure i.e., core + agents + CRDs and trigger experiments via CI/CD pipelines, without using the UI. I want a setup where chaos experiments can be created and executed programmatically, without deploying ChaosCenter. I noticed that Helm charts like litmus-core and litmus-agent exist, which suggests this deployment model is supported. However, there is no official guide or best practice document covering this approach. It seems that litmusctl can be used to manage infrastructure and experiments without the ChaosCenter. Would be great to provide related documentation.
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 litmuschaos/litmus, 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 litmuschaos/litmus acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 9.1% were successfully merged into the primary branch.
litmuschaos/litmus has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 hours. 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 52.1 places litmuschaos/litmus in the Solid tier.
The external pull request merge rate is 9.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, litmuschaos/litmus 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 litmuschaos/litmus 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.