litmuschaos/litmus
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 observed · 2026-08-28
Health v2 · maintenance only
93/100
- Activity 99
- Release rhythm 81
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: 30.5
- age_days: 3458
- days_rel: 49
- days_push: 8
- n_releases_24m: 21
Adoption not part of the score
5602 stars · 892 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
LitmusChaos is an open-source, CNCF-hosted chaos engineering platform for cloud-native Kubernetes infrastructure. It provides a ChaosCenter control plane for designing, scheduling, and observing chaos experiments, plus an execution plane of operators and agents that inject faults, with a large library of prebuilt experiments at ChaosHub.
Use cases
- inject pod and node faults into a kubernetes cluster to test resiliency
- run chaos experiments in CI/CD pipelines before releases
- verify that my application recovers from infrastructure failures
- schedule and monitor chaos workflows from a web UI
- automatically trigger chaos tests on deployment changes via GitOps
- validate SRE steady-state hypotheses with resilience probes
When to choose
- you run workloads on Kubernetes and want a mature, community-driven chaos engineering platform
- you want prebuilt fault experiments from ChaosHub instead of writing your own
- you need a web UI, GitOps integration, and observability dashboards for chaos testing
When to avoid
- your systems are not on Kubernetes or cloud-native infrastructure
- you only need simple load or unit testing rather than fault injection
- you cannot grant the cluster permissions chaos operators require
Facets
application · maturity stable
testing monitoring deployment workflow-automation container-orchestration cloud-computing monitoring self-hosted self-hosted cloud go chaos-engineering fault-injection resilience-testing sre cncf chaoshub gitops kubernetes-operator mcp-server devops containers kubernetes docker
9 sources
- readme: https://github.com/litmuschaos/litmus · fetched 2026-08-28 · 3341b2846fef
- homepage: https://litmuschaos.io · fetched 2026-08-29 · 6225e42f4721
- site_page: https://docs.litmuschaos.io/ · fetched 2026-08-29 · 84413c1e046f
- site_page: https://docs.litmuschaos.io/docs/getting-started/installation · fetched 2026-08-29 · 575788e88717
- site_page: https://docs.litmuschaos.io/docs/user-guides/observability-set-up · fetched 2026-08-29 · d678bfafcb3e
- site_page: https://docs.litmuschaos.io/docs/concepts/gitops · fetched 2026-08-29 · f7e79ad72300
- site_page: https://docs.litmuschaos.io/docs/user-guides/overview · fetched 2026-08-29 · 96f6e6ded97b
- site_page: https://docs.litmuschaos.io/docs/architecture/overview · fetched 2026-08-29 · 7b676ad554ce
- site_page: https://docs.litmuschaos.io/docs/introduction/other-links · fetched 2026-08-29 · c940e36acb28
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| litmuschaos/litmus | main | 93 |
For agents
markdown · JSON · MCP: product_card(name="litmuschaos/litmus")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem