Skip to content
DevUtils Online

Workflow Automation

cli vs puppeteer

puppeteer leads by 7.4 · clear

A

cli

91.7

32,362 stars · Apache-2.0

B · leads

puppeteer

99.1

95,849 stars · Apache-2.0

cli versus puppeteer 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; puppeteer is written mainly in TypeScript. The composite score is 91.7 for cli and 99.1 for puppeteer.

puppeteer has 95,849 GitHub stars to cli's 32,362, a gap of 63,487 (2.96×). Forks are 1,997 for cli and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 83 versus 100.

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

Both cli and puppeteer 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 puppeteer (95,849 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, puppeteer is open source.

puppeteer is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 17 points (83 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

puppeteer finishes ahead at 99.1 against cli at 91.7, a 7.4 point clear 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 puppeteer metrics
Signal cli puppeteer
GitHub stars 32,362 95,849
Forks 1,997 9,607
Open issues 137 201
Adoption 90 100
Activity 92 100
Community 83 100
Issue health 96 96
License 96 96
Self-hosting 100 100
Composite 91.7 99.1

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

puppeteer has more GitHub stars: 95,849 versus 32,362 for cli. The gap is 63,487 stars.

Which was updated more recently, cli or puppeteer?

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

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

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. puppeteer 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 puppeteer score?

puppeteer scores 99.1 and cli scores 91.7. This page calls that a clear lead for puppeteer.

Related comparisons