A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 18.4 · decisive
A · leads
99.1
72,721 stars · MIT
B
80.7
8,090 stars · MIT
act versus wasm3 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; wasm3 is written mainly in C. The composite score is 99.1 for act and 80.7 for wasm3.
act has 72,721 GitHub stars to wasm3's 8,090, a gap of 64,631 (8.99×). Forks are 2,126 for act and 537 for wasm3. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 82.
Push history: act was last pushed on 16 November 2026 (1 day ago), and wasm3 was last pushed on 30 September 2026 (47 days ago). Open issues stand at 318 for act (0.004 per star) and 21 for wasm3 (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 58.
Both act and wasm3 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 wasm3 (8,090 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, wasm3 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 42 points (100 vs 58), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against wasm3 at 80.7, a 18.4 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 | wasm3 |
|---|---|---|
| GitHub stars | 72,721 | 8,090 |
| Forks | 2,126 | 537 |
| Open issues | 318 | 21 |
| Adoption | 100 | 80 |
| Activity | 100 | 58 |
| Community | 100 | 82 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 80.7 |
Run your GitHub Actions locally 🚀
🚀 A fast WebAssembly interpreter and the most universal WASM runtime
act has more GitHub stars: 72,721 versus 8,090 for wasm3. The gap is 64,631 stars.
act was pushed more recently: 16 November 2026 versus 30 September 2026 for wasm3. That is 46 days apart.
Yes. This catalog marks both act and wasm3 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. wasm3 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 wasm3 scores 80.7. This page calls that a decisive lead for act.