A · leads
act
99.1
72,721 stars · MIT
DevOps
act leads by 10.8 · clear
A · leads
99.1
72,721 stars · MIT
B
88.3
12,143 stars · Apache-2.0
act versus kubeshark 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 88.3 for kubeshark.
act has 72,721 GitHub stars to kubeshark's 12,143, a gap of 60,578 (5.99×). Forks are 2,126 for act and 557 for kubeshark. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 82.
Push history: act was last pushed on 16 November 2026 (1 day ago), and kubeshark was last pushed on 10 November 2026 (7 days ago). Open issues stand at 318 for act (0.004 per star) and 145 for kubeshark (0.012 per star). Issue-health scores are 96 and 84; activity scores are 100 and 92.
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. kubeshark 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 kubeshark. This is a procurement signal, not legal advice.
In DevOps, both act (72,721 stars) and kubeshark (12,143 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, kubeshark is open source.
act is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 18 points (100 vs 82), and the tightest is self-hosting at 0 points (100 vs 100).
act finishes ahead at 99.1 against kubeshark at 88.3, a 10.8 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 | kubeshark |
|---|---|---|
| GitHub stars | 72,721 | 12,143 |
| Forks | 2,126 | 557 |
| Open issues | 318 | 145 |
| Adoption | 100 | 84 |
| Activity | 100 | 92 |
| Community | 100 | 82 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 88.3 |
Run your GitHub Actions locally 🚀
eBPF-powered network observability for Kubernetes. Indexes L4/L7 traffic with full K8s context, decrypts TLS without keys. Queryable by AI agents via MCP and humans via dashboard.
act has more GitHub stars: 72,721 versus 12,143 for kubeshark. The gap is 60,578 stars.
act was pushed more recently: 16 November 2026 versus 10 November 2026 for kubeshark. That is 6 days apart.
Yes. This catalog marks both act and kubeshark 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. kubeshark 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 kubeshark scores 88.3. This page calls that a clear lead for act.