A
cli
78.1
38,719 stars · BSD-3-Clause
DevOps
jenkins leads by 13.6 · clear
A
78.1
38,719 stars · BSD-3-Clause
B · leads
91.7
26,788 stars · MIT
cli versus jenkins 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; jenkins is written mainly in Java. The composite score is 78.1 for cli and 91.7 for jenkins.
cli has 38,719 GitHub stars to jenkins's 26,788, a gap of 11,931 (1.45×). Forks are 4,123 for cli and 9,837 for jenkins. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 90 versus 100.
Push history: cli was last pushed on 17 December 2024 (700 days ago), and jenkins was last pushed on 17 November 2026 (0 days ago). Open issues stand at 365 for cli (0.009 per star) and 3,618 for jenkins (0.135 per star). Issue-health scores are 84 and 34; 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. 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. License scores in this pair are 96 for cli and 96 for jenkins. This is a procurement signal, not legal advice.
In DevOps, both cli (38,719 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: cli is open source, jenkins is open source.
The lead is split. cli is furthest ahead on issue health (84 to 34), while jenkins is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
jenkins finishes ahead at 91.7 against cli at 78.1, a 13.6 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 | jenkins |
|---|---|---|
| GitHub stars | 38,719 | 26,788 |
| Forks | 4,123 | 9,837 |
| Open issues | 365 | 3,618 |
| Adoption | 100 | 96 |
| Activity | 16 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 78.1 | 91.7 |
🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.
Jenkins automation server
cli has more GitHub stars: 38,719 versus 26,788 for jenkins. The gap is 11,931 stars.
jenkins 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 jenkins 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. 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.
jenkins scores 91.7 and cli scores 78.1. This page calls that a clear lead for jenkins.