Skip to content
DevUtils Online

DevOps

jenkins vs semaphore

jenkins leads by 3.3 · narrow

A · leads

jenkins

92.9

26,788 stars · MIT

jenkins versus semaphore is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. jenkins is written mainly in Java; semaphore is written mainly in Go. The composite score is 92.9 for jenkins and 89.6 for semaphore.

jenkins has 26,788 GitHub stars to semaphore's 14,420, a gap of 12,368 (1.86×). Forks are 9,837 for jenkins and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 78.

Push history: jenkins was last pushed on 17 November 2026 (0 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,618 for jenkins (0.135 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 34 and 52; activity scores are 100 and 100.

Both jenkins and semaphore 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 jenkins (26,788 stars) and semaphore (14,420 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: jenkins is open source, semaphore is open source.

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

jenkins finishes ahead at 92.9 against semaphore at 89.6, a 3.3 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.

jenkins versus semaphore metrics
Signal jenkins semaphore
GitHub stars 26,788 14,420
Forks 9,837 1,353
Open issues 3,618 1,075
Adoption 100 94
Activity 100 100
Community 100 78
Issue health 34 52
License 96 96
Self-hosting 100 100
Composite 92.9 89.6

semaphore

Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, jenkins or semaphore?

jenkins has more GitHub stars: 26,788 versus 14,420 for semaphore. The gap is 12,368 stars.

Which was updated more recently, jenkins or semaphore?

Both were last pushed on 17 November 2026.

Can I self-host both jenkins and semaphore?

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

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

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. semaphore 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 jenkins vs semaphore score?

jenkins scores 92.9 and semaphore scores 89.6. This page calls that a narrow lead for jenkins.

Related comparisons