A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 21.0 · decisive
A · leads
96.5
59,134 stars · MIT
B
75.5
8,981 stars · AGPL-3.0
Gitea versus Yearning 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 75.5 for Yearning.
Gitea has 59,134 GitHub stars to Yearning's 8,981, a gap of 50,153 (6.58×). Forks are 7,414 for Gitea and 2,032 for Yearning. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 86.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and Yearning was last pushed on 24 August 2026 (85 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 164 for Yearning (0.018 per star). Issue-health scores are 70 and 84; 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. Yearning is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for Gitea and 52 for Yearning. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and Yearning (8,981 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, Yearning is open source.
The lead is split. Gitea is furthest ahead on license flexibility (96 to 52), while Yearning is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against Yearning at 75.5, a 21.0 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 | Yearning |
|---|---|---|
| GitHub stars | 59,134 | 8,981 |
| Forks | 7,414 | 2,032 |
| Open issues | 2,172 | 164 |
| Adoption | 100 | 83 |
| Activity | 100 | 58 |
| Community | 100 | 86 |
| Issue health | 70 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 75.5 |
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 most popular sql audit platform for mysql
Gitea has more GitHub stars: 59,134 versus 8,981 for Yearning. The gap is 50,153 stars.
Gitea was pushed more recently: 17 November 2026 versus 24 August 2026 for Yearning. That is 85 days apart.
Yes. This catalog marks both Gitea and Yearning 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. Yearning is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Gitea scores 96.5 and Yearning scores 75.5. This page calls that a decisive lead for Gitea.