Skip to content
DevUtils Online

DevOps

cli vs lens

cli leads by 6.5 · narrow

A · leads

cli

79.4

38,719 stars · BSD-3-Clause

B

lens

72.9

23,248 stars · MIT

cli versus lens 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; lens is written mainly in an unspecified language. The composite score is 79.4 for cli and 72.9 for lens.

cli has 38,719 GitHub stars to lens's 23,248, a gap of 15,471 (1.67×). Forks are 4,123 for cli and 1,466 for lens. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 88.

Push history: cli was last pushed on 17 December 2024 (700 days ago), and lens was last pushed on 11 February 2025 (644 days ago). Open issues stand at 365 for cli (0.009 per star) and 1,165 for lens (0.050 per star). Issue-health scores are 84 and 52; activity scores are 16 and 16.

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. 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. License scores in this pair are 96 for cli and 96 for lens. This is a procurement signal, not legal advice.

In DevOps, both cli (38,719 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: cli is open source, lens is open source.

cli is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 32 points (84 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).

cli finishes ahead at 79.4 against lens at 72.9, a 6.5 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.

cli versus lens metrics
Signal cli lens
GitHub stars 38,719 23,248
Forks 4,123 1,466
Open issues 365 1,165
Adoption 100 95
Activity 16 16
Community 100 88
Issue health 84 52
License 96 96
Self-hosting 100 100
Composite 79.4 72.9

cli

🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cli or lens?

cli has more GitHub stars: 38,719 versus 23,248 for lens. The gap is 15,471 stars.

Which was updated more recently, cli or lens?

lens was pushed more recently: 11 February 2025 versus 17 December 2024 for cli. That is 56 days apart.

Can I self-host both cli and lens?

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

Which license is easier to embed in a commercial product, cli or lens?

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. 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.

Who wins the cli vs lens score?

cli scores 79.4 and lens scores 72.9. This page calls that a narrow lead for cli.

Related comparisons