A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 9.3 · clear
A · leads
96.5
59,134 stars · MIT
B
87.2
12,143 stars · Apache-2.0
Gitea versus kubeshark 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.2 for kubeshark.
Gitea has 59,134 GitHub stars to kubeshark's 12,143, a gap of 46,991 (4.87×). Forks are 7,414 for Gitea and 557 for kubeshark. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 71.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and kubeshark was last pushed on 10 November 2026 (7 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 145 for kubeshark (0.012 per star). Issue-health scores are 70 and 84; activity scores are 100 and 92.
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. kubeshark 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 kubeshark. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and kubeshark (12,143 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, kubeshark is open source.
The lead is split. Gitea is furthest ahead on fork community (100 to 71), while kubeshark is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against kubeshark at 87.2, a 9.3 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 | kubeshark |
|---|---|---|
| GitHub stars | 59,134 | 12,143 |
| Forks | 7,414 | 557 |
| Open issues | 2,172 | 145 |
| Adoption | 100 | 86 |
| Activity | 100 | 92 |
| Community | 100 | 71 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 87.2 |
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.
eBPF-powered network observability for Kubernetes. Indexes L4/L7 traffic with full K8s context, decrypts TLS without keys. Queryable by AI agents via MCP and humans via dashboard.
Gitea has more GitHub stars: 59,134 versus 12,143 for kubeshark. The gap is 46,991 stars.
Gitea was pushed more recently: 17 November 2026 versus 10 November 2026 for kubeshark. That is 7 days apart.
Yes. This catalog marks both Gitea and kubeshark 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. kubeshark 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 kubeshark scores 87.2. This page calls that a clear lead for Gitea.