A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 26.8 · decisive
A · leads
99.1
72,721 stars · MIT
B
72.3
5,333 stars · Apache-2.0
act versus ThreatMapper 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; ThreatMapper is written mainly in TypeScript. The composite score is 99.1 for act and 72.3 for ThreatMapper.
act has 72,721 GitHub stars to ThreatMapper's 5,333, a gap of 67,388 (13.64×). Forks are 2,126 for act and 631 for ThreatMapper. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 84.
Push history: act was last pushed on 16 November 2026 (1 day ago), and ThreatMapper was last pushed on 01 June 2026 (169 days ago). Open issues stand at 318 for act (0.004 per star) and 144 for ThreatMapper (0.027 per star). Issue-health scores are 96 and 70; activity scores are 100 and 36.
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. ThreatMapper 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 ThreatMapper. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and ThreatMapper (5,333 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, ThreatMapper is open source.
act is ahead on every scored dimension that is not level. Level dimensions: 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 ThreatMapper at 72.3, a 26.8 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 | ThreatMapper |
|---|---|---|
| GitHub stars | 72,721 | 5,333 |
| Forks | 2,126 | 631 |
| Open issues | 318 | 144 |
| Adoption | 100 | 77 |
| Activity | 100 | 36 |
| Community | 100 | 84 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 72.3 |
Run your GitHub Actions locally 🚀
Open Source Cloud Native Application Protection Platform (CNAPP)
act has more GitHub stars: 72,721 versus 5,333 for ThreatMapper. The gap is 67,388 stars.
act was pushed more recently: 16 November 2026 versus 01 June 2026 for ThreatMapper. That is 168 days apart.
Yes. This catalog marks both act and ThreatMapper 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. ThreatMapper 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 ThreatMapper scores 72.3. This page calls that a decisive lead for act.