A · level
puppeteer
98.7
95,849 stars · Apache-2.0
Workflow Automation
Too close to call · 98.7 to 99.1
A · level
98.7
95,849 stars · Apache-2.0
B · level
99.1
103,871 stars · BSD-3-Clause
puppeteer versus Scrapling 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; Scrapling is written mainly in Python. The composite score is 98.7 for puppeteer and 99.1 for Scrapling.
Scrapling has 103,871 GitHub stars to puppeteer's 95,849, a gap of 8,022 (1.08×). Forks are 9,607 for puppeteer and 10,835 for Scrapling. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 99 versus 100.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and Scrapling was last pushed on 17 November 2026 (0 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 21 for Scrapling (0.000 per star). Issue-health scores are 96 and 96; 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. Scrapling is listed as BSD-3-Clause, 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 puppeteer and 96 for Scrapling. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and Scrapling (103,871 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, Scrapling is open source.
Scrapling is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 1 points (99 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Composite score: puppeteer 98.7, Scrapling 99.1. 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 | puppeteer | Scrapling |
|---|---|---|
| GitHub stars | 95,849 | 103,871 |
| Forks | 9,607 | 10,835 |
| Open issues | 201 | 21 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.7 | 99.1 |
JavaScript API for Chrome and Firefox
🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Scrapling has more GitHub stars: 103,871 versus 95,849 for puppeteer. The gap is 8,022 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both puppeteer and Scrapling as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Scrapling is listed as BSD-3-Clause, 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. puppeteer scores 98.7 and Scrapling scores 99.1.