Skip to content
DevUtils Online

DevOps

lens vs semaphore

semaphore leads by 16.7 · decisive

A

lens

76.2

23,248 stars · MIT

B · leads

semaphore

92.9

14,420 stars · MIT

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

lens has 23,248 GitHub stars to semaphore's 14,420, a gap of 8,828 (1.61×). Forks are 1,466 for lens and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 99.

Push history: lens was last pushed on 11 February 2025 (644 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,165 for lens (0.050 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 52 and 52; activity scores are 16 and 100.

Both lens 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 lens (23,248 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: lens is open source, semaphore is open source.

The lead is split. lens is furthest ahead on adoption (100 to 95), while semaphore is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.

semaphore finishes ahead at 92.9 against lens at 76.2, a 16.7 point decisive 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.

lens versus semaphore metrics
Signal lens semaphore
GitHub stars 23,248 14,420
Forks 1,466 1,353
Open issues 1,165 1,075
Adoption 100 95
Activity 16 100
Community 100 99
Issue health 52 52
License 96 96
Self-hosting 100 100
Composite 76.2 92.9

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, lens or semaphore?

lens has more GitHub stars: 23,248 versus 14,420 for semaphore. The gap is 8,828 stars.

Which was updated more recently, lens or semaphore?

semaphore was pushed more recently: 17 November 2026 versus 11 February 2025 for lens. That is 644 days apart.

Can I self-host both lens and semaphore?

Yes. This catalog marks both lens 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, lens or semaphore?

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

semaphore scores 92.9 and lens scores 76.2. This page calls that a decisive lead for semaphore.

Related comparisons