A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 7.1 · clear
A · leads
99.1
72,721 stars · MIT
B
92.0
16,623 stars · Apache-2.0
act versus dagger 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 92.0 for dagger.
act has 72,721 GitHub stars to dagger's 16,623, a gap of 56,098 (4.37×). Forks are 2,126 for act and 960 for dagger. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 90.
Push history: act was last pushed on 16 November 2026 (1 day ago), and dagger was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 266 for dagger (0.016 per star). Issue-health scores are 96 and 84; 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. dagger 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 dagger. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and dagger (16,623 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, dagger 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 adoption at 13 points (100 vs 87), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against dagger at 92.0, a 7.1 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 | dagger |
|---|---|---|
| GitHub stars | 72,721 | 16,623 |
| Forks | 2,126 | 960 |
| Open issues | 318 | 266 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 92.0 |
Run your GitHub Actions locally 🚀
Automation engine to build, test and ship any codebase. Runs locally, in CI, or directly in the cloud
act has more GitHub stars: 72,721 versus 16,623 for dagger. The gap is 56,098 stars.
dagger 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 dagger 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. dagger 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 dagger scores 92.0. This page calls that a clear lead for act.