Skip to content
DevUtils Online

DevOps

cli vs kubesphere

cli leads by 13.4 · clear

A · leads

cli

79.4

38,719 stars · BSD-3-Clause

cli versus kubesphere 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; kubesphere is written mainly in Go. The composite score is 79.4 for cli and 66.0 for kubesphere.

cli has 38,719 GitHub stars to kubesphere's 17,080, a gap of 21,639 (2.27×). Forks are 4,123 for cli and 2,752 for kubesphere. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 95.

Push history: cli was last pushed on 17 December 2024 (700 days ago), and kubesphere was last pushed on 15 July 2026 (125 days ago). Open issues stand at 365 for cli (0.009 per star) and 350 for kubesphere (0.020 per star). Issue-health scores are 84 and 70; activity scores are 16 and 36.

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. kubesphere is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for cli and 30 for kubesphere. This is a procurement signal, not legal advice.

Only cli is marked self-hostable here (38,719 stars, deploy score 100). kubesphere is not (17,080 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cli is open source, kubesphere is unpriced in this catalog.

The lead is split. cli is furthest ahead on license flexibility (96 to 30), while kubesphere is furthest ahead on recent activity (36 to 16). Choose the dimension a rollout cannot compromise on.

cli finishes ahead at 79.4 against kubesphere at 66.0, a 13.4 point clear 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 kubesphere metrics
Signal cli kubesphere
GitHub stars 38,719 17,080
Forks 4,123 2,752
Open issues 365 350
Adoption 100 92
Activity 16 36
Community 100 95
Issue health 84 70
License 96 30
Self-hosting 100 35
Composite 79.4 66.0

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

kubesphere

The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cli or kubesphere?

cli has more GitHub stars: 38,719 versus 17,080 for kubesphere. The gap is 21,639 stars.

Which was updated more recently, cli or kubesphere?

kubesphere was pushed more recently: 15 July 2026 versus 17 December 2024 for cli. That is 575 days apart.

Can I self-host both cli and kubesphere?

Only cli is marked self-hostable. kubesphere is not.

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

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. kubesphere is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the cli vs kubesphere score?

cli scores 79.4 and kubesphere scores 66.0. This page calls that a clear lead for cli.

Related comparisons