A · level
cli
97.4
32,362 stars · Apache-2.0
Workflow Automation
Too close to call · 97.4 to 96.8
A · level
97.4
32,362 stars · Apache-2.0
B · level
96.8
24,177 stars · MIT
cli versus semantic-release 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; semantic-release is written mainly in JavaScript. The composite score is 97.4 for cli and 96.8 for semantic-release.
cli has 32,362 GitHub stars to semantic-release's 24,177, a gap of 8,185 (1.34×). Forks are 1,997 for cli and 1,807 for semantic-release. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 99.
Push history: cli was last pushed on 03 November 2026 (14 days ago), and semantic-release was last pushed on 17 November 2026 (0 days ago). Open issues stand at 137 for cli (0.004 per star) and 410 for semantic-release (0.017 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
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. semantic-release 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 semantic-release. This is a procurement signal, not legal advice.
In Workflow Automation, both cli (32,362 stars) and semantic-release (24,177 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, semantic-release is open source.
The lead is split. cli is furthest ahead on issue health (96 to 84), while semantic-release is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
Composite score: cli 97.4, semantic-release 96.8. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | semantic-release |
|---|---|---|
| GitHub stars | 32,362 | 24,177 |
| Forks | 1,997 | 1,807 |
| Open issues | 137 | 410 |
| Adoption | 100 | 97 |
| Activity | 92 | 100 |
| Community | 100 | 99 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 96.8 |
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.
📦🚀 Fully automated version management and package publishing
cli has more GitHub stars: 32,362 versus 24,177 for semantic-release. The gap is 8,185 stars.
semantic-release was pushed more recently: 17 November 2026 versus 03 November 2026 for cli. That is 14 days apart.
Yes. This catalog marks both cli and semantic-release 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. semantic-release 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.
Neither tool clears a one-point margin. cli scores 97.4 and semantic-release scores 96.8.