Skip to content
DevUtils Online

DevOps

act vs jenkins

act leads by 6.9 · narrow

A · leads

act

96.8

72,721 stars · MIT

B

jenkins

89.9

26,788 stars · MIT

act versus jenkins 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; jenkins is written mainly in Java. The composite score is 96.8 for act and 89.9 for jenkins.

act has 72,721 GitHub stars to jenkins's 26,788, a gap of 45,933 (2.71×). Forks are 2,126 for act and 9,837 for jenkins. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 83 versus 100.

Push history: act was last pushed on 16 November 2026 (1 day ago), and jenkins was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for act (0.004 per star) and 3,618 for jenkins (0.135 per star). Issue-health scores are 96 and 34; activity scores are 100 and 100.

Both act and jenkins 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 jenkins (26,788 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, jenkins is open source.

The lead is split. act is furthest ahead on issue health (96 to 34), while jenkins is furthest ahead on fork community (100 to 83). Choose the dimension a rollout cannot compromise on.

act finishes ahead at 96.8 against jenkins at 89.9, a 6.9 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

act versus jenkins metrics
Signal act jenkins
GitHub stars 72,721 26,788
Forks 2,126 9,837
Open issues 318 3,618
Adoption 100 91
Activity 100 100
Community 83 100
Issue health 96 34
License 96 96
Self-hosting 100 100
Composite 96.8 89.9

Questions this page answers

Which has more GitHub stars, act or jenkins?

act has more GitHub stars: 72,721 versus 26,788 for jenkins. The gap is 45,933 stars.

Which was updated more recently, act or jenkins?

jenkins was pushed more recently: 17 November 2026 versus 16 November 2026 for act. That is 1 days apart.

Can I self-host both act and jenkins?

Yes. This catalog marks both act and jenkins as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, act or jenkins?

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. jenkins 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.

Who wins the act vs jenkins score?

act scores 96.8 and jenkins scores 89.9. This page calls that a narrow lead for act.

Related comparisons