A · leads
cli
96.0
32,362 stars · Apache-2.0
Workflow Automation
cli leads by 1.8 · narrow
A · leads
96.0
32,362 stars · Apache-2.0
B
94.2
27,230 stars · MIT
cli versus vagrant is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cli is written mainly in Rust; vagrant is written mainly in Ruby. The composite score is 96.0 for cli and 94.2 for vagrant.
cli has 32,362 GitHub stars to vagrant's 27,230, a gap of 5,132 (1.19×). Forks are 1,997 for cli and 4,491 for vagrant. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 90 versus 100.
Push history: cli was last pushed on 03 November 2026 (14 days ago), and vagrant was last pushed on 12 November 2026 (5 days ago). Open issues stand at 137 for cli (0.004 per star) and 760 for vagrant (0.028 per star). Issue-health scores are 96 and 70; activity scores are 92 and 92.
cli 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. vagrant 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 vagrant. This is a procurement signal, not legal advice.
In Workflow Automation, both cli (32,362 stars) and vagrant (27,230 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, vagrant is open source.
The lead is split. cli is furthest ahead on issue health (96 to 70), while vagrant is furthest ahead on fork community (100 to 90). Choose the dimension a rollout cannot compromise on.
cli finishes ahead at 96.0 against vagrant at 94.2, a 1.8 point narrow 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 | vagrant |
|---|---|---|
| GitHub stars | 32,362 | 27,230 |
| Forks | 1,997 | 4,491 |
| Open issues | 137 | 760 |
| Adoption | 100 | 98 |
| Activity | 92 | 92 |
| Community | 90 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.0 | 94.2 |
Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent skills.
Vagrant is a tool for building and distributing development environments.
cli has more GitHub stars: 32,362 versus 27,230 for vagrant. The gap is 5,132 stars.
vagrant was pushed more recently: 12 November 2026 versus 03 November 2026 for cli. That is 9 days apart.
Yes. This catalog marks both cli and vagrant as self-hostable. Confirm each project's deploy docs before you plan a migration.
cli 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. vagrant 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.
cli scores 96.0 and vagrant scores 94.2. This page calls that a narrow lead for cli.