A
git-sim
76.2
4,695 stars · GPL-2.0
DevOps
Gitea leads by 20.3 · decisive
A
76.2
4,695 stars · GPL-2.0
B · leads
96.5
59,134 stars · MIT
git-sim versus Gitea is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. git-sim is written mainly in Python; Gitea is written mainly in Go. The composite score is 76.2 for git-sim and 96.5 for Gitea.
Gitea has 59,134 GitHub stars to git-sim's 4,695, a gap of 54,439 (12.60×). Forks are 127 for git-sim and 7,414 for Gitea. On the log scale used inside this pair, adoption is 77 versus 100, and the fork community is 54 versus 100.
Push history: git-sim was last pushed on 12 October 2026 (35 days ago), and Gitea was last pushed on 17 November 2026 (0 days ago). Open issues stand at 11 for git-sim (0.002 per star) and 2,172 for Gitea (0.037 per star). Issue-health scores are 96 and 70; activity scores are 78 and 100.
git-sim is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. License scores in this pair are 64 for git-sim and 96 for Gitea. This is a procurement signal, not legal advice.
In DevOps, both git-sim (4,695 stars) and Gitea (59,134 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: git-sim is open source, Gitea is open source.
The lead is split. git-sim is furthest ahead on issue health (96 to 70), while Gitea is furthest ahead on fork community (100 to 54). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against git-sim at 76.2, a 20.3 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 | git-sim | Gitea |
|---|---|---|
| GitHub stars | 4,695 | 59,134 |
| Forks | 127 | 7,414 |
| Open issues | 11 | 2,172 |
| Adoption | 77 | 100 |
| Activity | 78 | 100 |
| Community | 54 | 100 |
| Issue health | 96 | 70 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 76.2 | 96.5 |
The visual layer for Git in your own repos: simulate, record, replay, audit, and share entire Git workflows, wherever you or your agents run them.
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.
Gitea has more GitHub stars: 59,134 versus 4,695 for git-sim. The gap is 54,439 stars.
Gitea was pushed more recently: 17 November 2026 versus 12 October 2026 for git-sim. That is 35 days apart.
Yes. This catalog marks both git-sim and Gitea as self-hostable. Confirm each project's deploy docs before you plan a migration.
git-sim is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Gitea scores 96.5 and git-sim scores 76.2. This page calls that a decisive lead for Gitea.