Skip to content
DevUtils Online

Workflow Automation

cli vs sim

sim leads by 1.5 · narrow

A

cli

96.2

32,362 stars · Apache-2.0

B · leads

sim

97.7

30,151 stars · Apache-2.0

cli versus sim 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; sim is written mainly in TypeScript. The composite score is 96.2 for cli and 97.7 for sim.

cli has 32,362 GitHub stars to sim's 30,151, a gap of 2,211 (1.07×). Forks are 1,997 for cli and 3,915 for sim. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 92 versus 100.

Push history: cli was last pushed on 03 November 2026 (14 days ago), and sim was last pushed on 17 November 2026 (0 days ago). Open issues stand at 137 for cli (0.004 per star) and 330 for sim (0.011 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.

Both cli and sim are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

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

The lead is split. cli is furthest ahead on issue health (96 to 84), while sim is furthest ahead on fork community (100 to 92). Choose the dimension a rollout cannot compromise on.

sim finishes ahead at 97.7 against cli at 96.2, a 1.5 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 sim metrics
Signal cli sim
GitHub stars 32,362 30,151
Forks 1,997 3,915
Open issues 137 330
Adoption 100 99
Activity 92 100
Community 92 100
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 96.2 97.7

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

sim

Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cli or sim?

cli has more GitHub stars: 32,362 versus 30,151 for sim. The gap is 2,211 stars.

Which was updated more recently, cli or sim?

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

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

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. sim 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.

Who wins the cli vs sim score?

sim scores 97.7 and cli scores 96.2. This page calls that a narrow lead for sim.

Related comparisons