A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 9.5 · clear
A · leads
99.1
72,721 stars · MIT
B
89.6
9,162 stars · Apache-2.0
act versus checkov is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. act is written mainly in Go; checkov is written mainly in Python. The composite score is 99.1 for act and 89.6 for checkov.
act has 72,721 GitHub stars to checkov's 9,162, a gap of 63,559 (7.94×). Forks are 2,126 for act and 1,476 for checkov. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 95.
Push history: act was last pushed on 16 November 2026 (1 day ago), and checkov was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 227 for checkov (0.025 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
act 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. 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. License scores in this pair are 96 for act and 96 for checkov. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and checkov (9,162 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: act is open source, checkov is open source.
act is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against checkov at 89.6, a 9.5 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 | act | checkov |
|---|---|---|
| GitHub stars | 72,721 | 9,162 |
| Forks | 2,126 | 1,476 |
| Open issues | 318 | 227 |
| Adoption | 100 | 82 |
| Activity | 100 | 100 |
| Community | 100 | 95 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 89.6 |
Run your GitHub Actions locally 🚀
Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
act has more GitHub stars: 72,721 versus 9,162 for checkov. The gap is 63,559 stars.
checkov was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.
Yes. This catalog marks both act and checkov as self-hostable. Confirm each project's deploy docs before you plan a migration.
act 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
act scores 99.1 and checkov scores 89.6. This page calls that a clear lead for act.