Skip to content
DevUtils Online

Workflow Automation

cli vs skyvern

cli leads by 5.6 · narrow

A · leads

cli

97.2

32,362 stars · Apache-2.0

B

skyvern

91.6

23,434 stars · AGPL-3.0

cli versus skyvern 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; skyvern is written mainly in Python. The composite score is 97.2 for cli and 91.6 for skyvern.

cli has 32,362 GitHub stars to skyvern's 23,434, a gap of 8,928 (1.38×). Forks are 1,997 for cli and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 98 versus 100.

Push history: cli was last pushed on 03 November 2026 (14 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 137 for cli (0.004 per star) and 301 for skyvern (0.013 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for cli and 52 for skyvern. This is a procurement signal, not legal advice.

In Workflow Automation, both cli (32,362 stars) and skyvern (23,434 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, skyvern is open source.

The lead is split. cli is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.

cli finishes ahead at 97.2 against skyvern at 91.6, a 5.6 point narrow 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 skyvern metrics
Signal cli skyvern
GitHub stars 32,362 23,434
Forks 1,997 2,246
Open issues 137 301
Adoption 100 97
Activity 92 100
Community 98 100
Issue health 96 84
License 96 52
Self-hosting 100 100
Composite 97.2 91.6

cli

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cli or skyvern?

cli has more GitHub stars: 32,362 versus 23,434 for skyvern. The gap is 8,928 stars.

Which was updated more recently, cli or skyvern?

skyvern was pushed more recently: 17 November 2026 versus 03 November 2026 for cli. That is 14 days apart.

Can I self-host both cli and skyvern?

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

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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the cli vs skyvern score?

cli scores 97.2 and skyvern scores 91.6. This page calls that a narrow lead for cli.

Related comparisons