A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 16.0 · decisive
A · leads
96.5
59,134 stars · MIT
B
80.5
12,222 stars · MIT
Gitea versus webhook 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 80.5 for webhook.
Gitea has 59,134 GitHub stars to webhook's 12,222, a gap of 46,912 (4.84×). Forks are 7,414 for Gitea and 884 for webhook. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 76.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and webhook was last pushed on 04 September 2026 (74 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 131 for webhook (0.011 per star). Issue-health scores are 70 and 84; activity scores are 100 and 58.
Both Gitea and webhook 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 webhook (12,222 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, webhook is open source.
The lead is split. Gitea is furthest ahead on recent activity (100 to 58), while webhook is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against webhook at 80.5, a 16.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 | webhook |
|---|---|---|
| GitHub stars | 59,134 | 12,222 |
| Forks | 7,414 | 884 |
| Open issues | 2,172 | 131 |
| Adoption | 100 | 86 |
| Activity | 100 | 58 |
| Community | 100 | 76 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 80.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.
webhook is a lightweight incoming webhook server to run shell commands
Gitea has more GitHub stars: 59,134 versus 12,222 for webhook. The gap is 46,912 stars.
Gitea was pushed more recently: 17 November 2026 versus 04 September 2026 for webhook. That is 74 days apart.
Yes. This catalog marks both Gitea and webhook 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. webhook 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 webhook scores 80.5. This page calls that a decisive lead for Gitea.