A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 8.8 · clear
A · leads
96.5
59,134 stars · MIT
B
87.7
14,420 stars · MIT
Gitea versus semaphore 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 87.7 for semaphore.
Gitea has 59,134 GitHub stars to semaphore's 14,420, a gap of 44,714 (4.10×). Forks are 7,414 for Gitea and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 81.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
Both Gitea and semaphore are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and semaphore (14,420 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, semaphore is open source.
Gitea is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 19 points (100 vs 81), and the tightest is self-hosting at 0 points (100 vs 100).
Gitea finishes ahead at 96.5 against semaphore at 87.7, a 8.8 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 | semaphore |
|---|---|---|
| GitHub stars | 59,134 | 14,420 |
| Forks | 7,414 | 1,353 |
| Open issues | 2,172 | 1,075 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 87.7 |
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.
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
Gitea has more GitHub stars: 59,134 versus 14,420 for semaphore. The gap is 44,714 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and semaphore 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. semaphore 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Gitea scores 96.5 and semaphore scores 87.7. This page calls that a clear lead for Gitea.