A
checkov
88.2
9,162 stars · Apache-2.0
DevOps
Gitea leads by 8.3 · clear
A
88.2
9,162 stars · Apache-2.0
B · leads
96.5
59,134 stars · MIT
checkov versus Gitea is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. checkov is written mainly in Python; Gitea is written mainly in Go. The composite score is 88.2 for checkov and 96.5 for Gitea.
Gitea has 59,134 GitHub stars to checkov's 9,162, a gap of 49,972 (6.45×). Forks are 1,476 for checkov and 7,414 for Gitea. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 82 versus 100.
Push history: checkov was last pushed on 17 November 2026 (0 days ago), and Gitea was last pushed on 17 November 2026 (0 days ago). Open issues stand at 227 for checkov (0.025 per star) and 2,172 for Gitea (0.037 per star). Issue-health scores are 70 and 70; activity scores are 100 and 100.
checkov 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. 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 96 for checkov and 96 for Gitea. This is a procurement signal, not legal advice.
In DevOps, both checkov (9,162 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: checkov is open source, Gitea 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 18 points (82 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Gitea finishes ahead at 96.5 against checkov at 88.2, a 8.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 | checkov | Gitea |
|---|---|---|
| GitHub stars | 9,162 | 59,134 |
| Forks | 1,476 | 7,414 |
| Open issues | 227 | 2,172 |
| Adoption | 83 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.2 | 96.5 |
Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
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 9,162 for checkov. The gap is 49,972 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both checkov and Gitea as self-hostable. Confirm each project's deploy docs before you plan a migration.
checkov 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. 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 checkov scores 88.2. This page calls that a clear lead for Gitea.