A · leads
Gitea
96.5
59,134 stars · MIT
DevOps
Gitea leads by 6.5 · narrow
A · leads
96.5
59,134 stars · MIT
B
90.0
11,953 stars · Apache-2.0
Gitea versus kubescape 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 90.0 for kubescape.
Gitea has 59,134 GitHub stars to kubescape's 11,953, a gap of 47,181 (4.95×). Forks are 7,414 for Gitea and 1,110 for kubescape. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 79.
Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and kubescape was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 80 for kubescape (0.007 per star). Issue-health scores are 70 and 84; 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. kubescape 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 kubescape. This is a procurement signal, not legal advice.
In DevOps, both Gitea (59,134 stars) and kubescape (11,953 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, kubescape is open source.
The lead is split. Gitea is furthest ahead on fork community (100 to 79), while kubescape is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Gitea finishes ahead at 96.5 against kubescape at 90.0, a 6.5 point narrow 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 | kubescape |
|---|---|---|
| GitHub stars | 59,134 | 11,953 |
| Forks | 7,414 | 1,110 |
| Open issues | 2,172 | 80 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 90.0 |
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.
Kubescape is an open-source Kubernetes security platform for your IDE, CI/CD pipelines, and clusters. It includes risk analysis, security, compliance, and misconfiguration scanning, saving Kubernetes users and administrators precious time, effort, and resources.
Gitea has more GitHub stars: 59,134 versus 11,953 for kubescape. The gap is 47,181 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Gitea and kubescape 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. kubescape 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 kubescape scores 90.0. This page calls that a narrow lead for Gitea.