A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 22.1 · decisive
A · leads
96.5
59,134 stars · MIT
B
74.4
7,064 stars · MIT
Gitea versus tfsec 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 74.4 for tfsec.
Gitea has 59,134 GitHub stars to tfsec's 7,064, a gap of 52,070 (8.37×). Forks are 7,414 for Gitea and 560 for tfsec. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 71.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and tfsec was last pushed on 25 March 2026 (237 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 19 for tfsec (0.003 per star). Issue-health scores are 70 and 96; activity scores are 100 and 36.
Both Gitea and tfsec 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 tfsec (7,064 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, tfsec is open source.
The lead is split. Gitea is furthest ahead on recent activity (100 to 36), while tfsec is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against tfsec at 74.4, a 22.1 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 | tfsec |
|---|---|---|
| GitHub stars | 59,134 | 7,064 |
| Forks | 7,414 | 560 |
| Open issues | 2,172 | 19 |
| Adoption | 100 | 81 |
| Activity | 100 | 36 |
| Community | 100 | 71 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 74.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.
Tfsec is now part of Trivy
Gitea has more GitHub stars: 59,134 versus 7,064 for tfsec. The gap is 52,070 stars.
Gitea was pushed more recently: 17 November 2026 versus 25 March 2026 for tfsec. That is 237 days apart.
Yes. This catalog marks both Gitea and tfsec 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. tfsec 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 tfsec scores 74.4. This page calls that a decisive lead for Gitea.