A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 21.6 · decisive
A · leads
96.5
59,134 stars · MIT
B
74.9
9,848 stars · CC0-1.0
Gitea versus howtheysre is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Gitea is written mainly in Go; howtheysre is written mainly in JavaScript. The composite score is 96.5 for Gitea and 74.9 for howtheysre.
Gitea has 59,134 GitHub stars to howtheysre's 9,848, a gap of 49,286 (6.00×). Forks are 7,414 for Gitea and 902 for howtheysre. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 76.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and howtheysre was last pushed on 30 September 2026 (48 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 12 for howtheysre (0.001 per star). Issue-health scores are 70 and 96; activity scores are 100 and 58.
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. howtheysre is listed as CC0-1.0, which this catalog treats as custom terms. A public repository is not itself permission to embed the code. License scores in this pair are 96 for Gitea and 45 for howtheysre. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and howtheysre (9,848 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, howtheysre is open source.
The lead is split. Gitea is furthest ahead on license flexibility (96 to 45), while howtheysre is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against howtheysre at 74.9, a 21.6 point decisive 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 | howtheysre |
|---|---|---|
| GitHub stars | 59,134 | 9,848 |
| Forks | 7,414 | 902 |
| Open issues | 2,172 | 12 |
| Adoption | 100 | 84 |
| Activity | 100 | 58 |
| Community | 100 | 76 |
| Issue health | 70 | 96 |
| License | 96 | 45 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 74.9 |
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.
A curated collection of publicly available resources on how technology and tech-savvy organizations around the world practice Site Reliability Engineering (SRE)
Gitea has more GitHub stars: 59,134 versus 9,848 for howtheysre. The gap is 49,286 stars.
Gitea was pushed more recently: 17 November 2026 versus 30 September 2026 for howtheysre. That is 48 days apart.
Yes. This catalog marks both Gitea and howtheysre 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. howtheysre is listed as CC0-1.0, which this catalog treats as custom terms. A public repository is not itself permission to embed the code. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Gitea scores 96.5 and howtheysre scores 74.9. This page calls that a decisive lead for Gitea.