A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 23.6 · decisive
A · leads
99.1
72,721 stars · MIT
B
75.5
7,064 stars · MIT
act versus tfsec 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 99.1 for act and 75.5 for tfsec.
act has 72,721 GitHub stars to tfsec's 7,064, a gap of 65,657 (10.29×). Forks are 2,126 for act and 560 for tfsec. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 83.
Push history: act was last pushed on 16 November 2026 (1 day ago), and tfsec was last pushed on 25 March 2026 (237 days ago). Open issues stand at 318 for act (0.004 per star) and 19 for tfsec (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 36.
Both act and tfsec are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and tfsec (7,064 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, tfsec is open source.
act is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 64 points (100 vs 36), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against tfsec at 75.5, a 23.6 point decisive 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 | tfsec |
|---|---|---|
| GitHub stars | 72,721 | 7,064 |
| Forks | 2,126 | 560 |
| Open issues | 318 | 19 |
| Adoption | 100 | 79 |
| Activity | 100 | 36 |
| Community | 100 | 83 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 75.5 |
Run your GitHub Actions locally 🚀
Tfsec is now part of Trivy
act has more GitHub stars: 72,721 versus 7,064 for tfsec. The gap is 65,657 stars.
act was pushed more recently: 16 November 2026 versus 25 March 2026 for tfsec. That is 236 days apart.
Yes. This catalog marks both act and tfsec 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. tfsec 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.
act scores 99.1 and tfsec scores 75.5. This page calls that a decisive lead for act.