Skip to content
DevUtils Online

Workflow Automation

puppeteer vs skyvern

puppeteer leads by 12.9 · clear

A · leads

puppeteer

99.1

95,849 stars · Apache-2.0

B

skyvern

86.2

23,434 stars · AGPL-3.0

puppeteer versus skyvern is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. puppeteer is written mainly in TypeScript; skyvern is written mainly in Python. The composite score is 99.1 for puppeteer and 86.2 for skyvern.

puppeteer has 95,849 GitHub stars to skyvern's 23,434, a gap of 72,415 (4.09×). Forks are 9,607 for puppeteer and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 84.

Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

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. 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 puppeteer and 52 for skyvern. This is a procurement signal, not legal advice.

In Workflow Automation, both puppeteer (95,849 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: puppeteer is open source, skyvern is open source.

puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).

puppeteer finishes ahead at 99.1 against skyvern at 86.2, a 12.9 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.

puppeteer versus skyvern metrics
Signal puppeteer skyvern
GitHub stars 95,849 23,434
Forks 9,607 2,246
Open issues 201 301
Adoption 100 88
Activity 100 100
Community 100 84
Issue health 96 84
License 96 52
Self-hosting 100 100
Composite 99.1 86.2

Questions this page answers

Which has more GitHub stars, puppeteer or skyvern?

puppeteer has more GitHub stars: 95,849 versus 23,434 for skyvern. The gap is 72,415 stars.

Which was updated more recently, puppeteer or skyvern?

Both were last pushed on 17 November 2026.

Can I self-host both puppeteer and skyvern?

Yes. This catalog marks both puppeteer 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, puppeteer or skyvern?

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

puppeteer scores 99.1 and skyvern scores 86.2. This page calls that a clear lead for puppeteer.

Related comparisons