A
cli
79.4
38,719 stars · BSD-3-Clause
DevOps
dagger leads by 13.4 · clear
A
79.4
38,719 stars · BSD-3-Clause
B · leads
92.8
16,623 stars · Apache-2.0
cli versus dagger 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; dagger is written mainly in Go. The composite score is 79.4 for cli and 92.8 for dagger.
cli has 38,719 GitHub stars to dagger's 16,623, a gap of 22,096 (2.33×). Forks are 4,123 for cli and 960 for dagger. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 82.
Push history: cli was last pushed on 17 December 2024 (700 days ago), and dagger was last pushed on 17 November 2026 (0 days ago). Open issues stand at 365 for cli (0.009 per star) and 266 for dagger (0.016 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. dagger is listed as Apache-2.0, 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 dagger. This is a procurement signal, not legal advice.
In DevOps, both cli (38,719 stars) and dagger (16,623 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, dagger is open source.
The lead is split. cli is furthest ahead on fork community (100 to 82), while dagger is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
dagger finishes ahead at 92.8 against cli at 79.4, a 13.4 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 | dagger |
|---|---|---|
| GitHub stars | 38,719 | 16,623 |
| Forks | 4,123 | 960 |
| Open issues | 365 | 266 |
| Adoption | 100 | 92 |
| Activity | 16 | 100 |
| Community | 100 | 82 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 79.4 | 92.8 |
🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.
Automation engine to build, test and ship any codebase. Runs locally, in CI, or directly in the cloud
cli has more GitHub stars: 38,719 versus 16,623 for dagger. The gap is 22,096 stars.
dagger 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 dagger 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. dagger is listed as Apache-2.0, 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.
dagger scores 92.8 and cli scores 79.4. This page calls that a clear lead for dagger.