A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 15.3 · decisive
A · leads
99.1
72,721 stars · MIT
B
83.8
8,012 stars · AGPL-3.0
act versus steampipe 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 83.8 for steampipe.
act has 72,721 GitHub stars to steampipe's 8,012, a gap of 64,709 (9.08×). Forks are 2,126 for act and 349 for steampipe. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 76.
Push history: act was last pushed on 16 November 2026 (1 day ago), and steampipe was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 35 for steampipe (0.004 per star). Issue-health scores are 96 and 96; 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. steampipe is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for act and 52 for steampipe. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and steampipe (8,012 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, steampipe is open source.
act is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against steampipe at 83.8, a 15.3 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 | steampipe |
|---|---|---|
| GitHub stars | 72,721 | 8,012 |
| Forks | 2,126 | 349 |
| Open issues | 318 | 35 |
| Adoption | 100 | 80 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 96 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 83.8 |
Run your GitHub Actions locally 🚀
Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
act has more GitHub stars: 72,721 versus 8,012 for steampipe. The gap is 64,709 stars.
steampipe 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 steampipe 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. steampipe is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
act scores 99.1 and steampipe scores 83.8. This page calls that a decisive lead for act.