A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 10.1 · clear
A · leads
99.1
72,721 stars · MIT
B
89.0
23,030 stars · Apache-2.0
act versus witr 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 89.0 for witr.
act has 72,721 GitHub stars to witr's 23,030, a gap of 49,691 (3.16×). Forks are 2,126 for act and 811 for witr. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 87.
Push history: act was last pushed on 16 November 2026 (1 day ago), and witr was last pushed on 23 October 2026 (25 days ago). Open issues stand at 318 for act (0.004 per star) and 8 for witr (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 78.
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. witr 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 witr. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and witr (23,030 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, witr 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 22 points (100 vs 78), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against witr at 89.0, a 10.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 | witr |
|---|---|---|
| GitHub stars | 72,721 | 23,030 |
| Forks | 2,126 | 811 |
| Open issues | 318 | 8 |
| Adoption | 100 | 90 |
| Activity | 100 | 78 |
| Community | 100 | 87 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 89.0 |
Run your GitHub Actions locally 🚀
Why is this running? Trace any process, port, container, or file back to what started it - CLI + TUI.
act has more GitHub stars: 72,721 versus 23,030 for witr. The gap is 49,691 stars.
act was pushed more recently: 16 November 2026 versus 23 October 2026 for witr. That is 24 days apart.
Yes. This catalog marks both act and witr 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. witr 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 witr scores 89.0. This page calls that a clear lead for act.