A · leads
jenkins
92.9
26,788 stars · MIT
DevOps
jenkins leads by 20.0 · decisive
A · leads
92.9
26,788 stars · MIT
B
72.9
23,248 stars · MIT
jenkins versus lens 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; lens is written mainly in an unspecified language. The composite score is 92.9 for jenkins and 72.9 for lens.
jenkins has 26,788 GitHub stars to lens's 23,248, a gap of 3,540 (1.15×). Forks are 9,837 for jenkins and 1,466 for lens. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 79.
Push history: jenkins was last pushed on 17 November 2026 (0 days ago), and lens was last pushed on 11 February 2025 (644 days ago). Open issues stand at 3,618 for jenkins (0.135 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 34 and 52; activity scores are 100 and 16.
Both jenkins and lens 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 lens (23,248 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, lens is open source.
The lead is split. jenkins is furthest ahead on recent activity (100 to 16), while lens is furthest ahead on issue health (52 to 34). Choose the dimension a rollout cannot compromise on.
jenkins finishes ahead at 92.9 against lens at 72.9, a 20.0 point decisive 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 | jenkins | lens |
|---|---|---|
| GitHub stars | 26,788 | 23,248 |
| Forks | 9,837 | 1,466 |
| Open issues | 3,618 | 1,165 |
| Adoption | 100 | 99 |
| Activity | 100 | 16 |
| Community | 100 | 79 |
| Issue health | 34 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 72.9 |
Jenkins automation server
Lens - The way the world runs Kubernetes
jenkins has more GitHub stars: 26,788 versus 23,248 for lens. The gap is 3,540 stars.
jenkins was pushed more recently: 17 November 2026 versus 11 February 2025 for lens. That is 644 days apart.
Yes. This catalog marks both jenkins and lens as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
jenkins scores 92.9 and lens scores 72.9. This page calls that a decisive lead for jenkins.