A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 14.1 · clear
A · leads
96.5
59,134 stars · MIT
B
82.4
5,747 stars · Apache-2.0
Gitea versus litmus is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Go. The composite score is 96.5 for Gitea and 82.4 for litmus.
Gitea has 59,134 GitHub stars to litmus's 5,747, a gap of 53,387 (10.29×). Forks are 7,414 for Gitea and 905 for litmus. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 76.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and litmus was last pushed on 05 November 2026 (12 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 427 for litmus (0.074 per star). Issue-health scores are 70 and 52; activity scores are 100 and 92.
Gitea is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. litmus is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 96 for Gitea and 96 for litmus. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and litmus (5,747 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Gitea is open source, litmus is open source.
Gitea is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 24 points (100 vs 76), and the tightest is self-hosting at 0 points (100 vs 100).
Gitea finishes ahead at 96.5 against litmus at 82.4, a 14.1 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Gitea | litmus |
|---|---|---|
| GitHub stars | 59,134 | 5,747 |
| Forks | 7,414 | 905 |
| Open issues | 2,172 | 427 |
| Adoption | 100 | 79 |
| Activity | 100 | 92 |
| Community | 100 | 76 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 82.4 |
Gitea is a lightweight self-hosted Git service with issues, pull requests, and actions. It is the usual choice when a team wants a small forge they can run themselves.
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
Gitea has more GitHub stars: 59,134 versus 5,747 for litmus. The gap is 53,387 stars.
Gitea was pushed more recently: 17 November 2026 versus 05 November 2026 for litmus. That is 12 days apart.
Yes. This catalog marks both Gitea and litmus as self-hostable. Confirm each project's deploy docs before you plan a migration.
Gitea is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. litmus is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Gitea scores 96.5 and litmus scores 82.4. This page calls that a clear lead for Gitea.