A
cli
79.4
38,719 stars · BSD-3-Clause
DevOps
semaphore leads by 10.3 · clear
A
79.4
38,719 stars · BSD-3-Clause
B · leads
89.7
14,420 stars · MIT
cli versus semaphore is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cli is written mainly in Python; semaphore is written mainly in Go. The composite score is 79.4 for cli and 89.7 for semaphore.
cli has 38,719 GitHub stars to semaphore's 14,420, a gap of 24,299 (2.69×). Forks are 4,123 for cli and 1,353 for semaphore. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 87.
Push history: cli was last pushed on 17 December 2024 (700 days ago), and semaphore was last pushed on 17 November 2026 (0 days ago). Open issues stand at 365 for cli (0.009 per star) and 1,075 for semaphore (0.075 per star). Issue-health scores are 84 and 52; activity scores are 16 and 100.
cli is listed as BSD-3-Clause, 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. License scores in this pair are 96 for cli and 96 for semaphore. This is a procurement signal, not legal advice.
In DevOps, both cli (38,719 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: cli is open source, semaphore is open source.
The lead is split. cli is furthest ahead on issue health (84 to 52), while semaphore is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
semaphore finishes ahead at 89.7 against cli at 79.4, a 10.3 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 | cli | semaphore |
|---|---|---|
| GitHub stars | 38,719 | 14,420 |
| Forks | 4,123 | 1,353 |
| Open issues | 365 | 1,075 |
| Adoption | 100 | 91 |
| Activity | 16 | 100 |
| Community | 100 | 87 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 79.4 | 89.7 |
🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.
Modern UI and powerful API for Ansible, Terraform/OpenTofu/Terragrunt, PowerShell and other DevOps tools.
cli has more GitHub stars: 38,719 versus 14,420 for semaphore. The gap is 24,299 stars.
semaphore was pushed more recently: 17 November 2026 versus 17 December 2024 for cli. That is 700 days apart.
Yes. This catalog marks both cli and semaphore as self-hostable. Confirm each project's deploy docs before you plan a migration.
cli is listed as BSD-3-Clause, 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.
semaphore scores 89.7 and cli scores 79.4. This page calls that a clear lead for semaphore.