Skip to content
DevUtils Online

DevOps

cli vs wtf

wtf leads by 11.1 · clear

A

cli

79.4

38,719 stars · BSD-3-Clause

B · leads

wtf

90.5

17,154 stars · MPL-2.0

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

cli has 38,719 GitHub stars to wtf's 17,154, a gap of 21,565 (2.26×). Forks are 4,123 for cli and 866 for wtf. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 81.

Push history: cli was last pushed on 17 December 2024 (700 days ago), and wtf was last pushed on 14 November 2026 (3 days ago). Open issues stand at 365 for cli (0.009 per star) and 107 for wtf (0.006 per star). Issue-health scores are 84 and 84; 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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for cli and 78 for wtf. This is a procurement signal, not legal advice.

In DevOps, both cli (38,719 stars) and wtf (17,154 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, wtf is open source.

The lead is split. cli is furthest ahead on fork community (100 to 81), while wtf is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.

wtf finishes ahead at 90.5 against cli at 79.4, a 11.1 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 wtf metrics
Signal cli wtf
GitHub stars 38,719 17,154
Forks 4,123 866
Open issues 365 107
Adoption 100 92
Activity 16 100
Community 100 81
Issue health 84 84
License 96 78
Self-hosting 100 100
Composite 79.4 90.5

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 wtf?

cli has more GitHub stars: 38,719 versus 17,154 for wtf. The gap is 21,565 stars.

Which was updated more recently, cli or wtf?

wtf was pushed more recently: 14 November 2026 versus 17 December 2024 for cli. That is 697 days apart.

Can I self-host both cli and wtf?

Yes. This catalog marks both cli and wtf 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 wtf?

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. wtf is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the cli vs wtf score?

wtf scores 90.5 and cli scores 79.4. This page calls that a clear lead for wtf.

Related comparisons