A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 9.7 · clear
A · leads
96.5
59,134 stars · MIT
B
86.8
8,208 stars · Apache-2.0
Gitea versus woodpecker 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 86.8 for woodpecker.
Gitea has 59,134 GitHub stars to woodpecker's 8,208, a gap of 50,926 (7.20×). Forks are 7,414 for Gitea and 750 for woodpecker. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 74.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and woodpecker was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 376 for woodpecker (0.046 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
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. woodpecker is listed as Apache-2.0, 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 96 for Gitea and 96 for woodpecker. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and woodpecker (8,208 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, woodpecker is open source.
Gitea is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 26 points (100 vs 74), and the tightest is self-hosting at 0 points (100 vs 100).
Gitea finishes ahead at 96.5 against woodpecker at 86.8, a 9.7 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 | woodpecker |
|---|---|---|
| GitHub stars | 59,134 | 8,208 |
| Forks | 7,414 | 750 |
| Open issues | 2,172 | 376 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 74 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 86.8 |
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.
Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.
Gitea has more GitHub stars: 59,134 versus 8,208 for woodpecker. The gap is 50,926 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and woodpecker 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. woodpecker is listed as Apache-2.0, 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 woodpecker scores 86.8. This page calls that a clear lead for Gitea.