A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 35.6 · decisive
A · leads
99.1
95,849 stars · Apache-2.0
B
63.5
12,914 stars · GPL-3.0
puppeteer versus undetected-chromedriver 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; undetected-chromedriver is written mainly in Python. The composite score is 99.1 for puppeteer and 63.5 for undetected-chromedriver.
puppeteer has 95,849 GitHub stars to undetected-chromedriver's 12,914, a gap of 82,935 (7.42×). Forks are 9,607 for puppeteer and 1,344 for undetected-chromedriver. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 79.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and undetected-chromedriver was last pushed on 05 July 2025 (500 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 1,142 for undetected-chromedriver (0.088 per star). Issue-health scores are 96 and 52; activity scores are 100 and 16.
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. undetected-chromedriver is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for puppeteer and 64 for undetected-chromedriver. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and undetected-chromedriver (12,914 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, undetected-chromedriver is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is recent activity at 84 points (100 vs 16), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against undetected-chromedriver at 63.5, a 35.6 point decisive margin under the published weights.
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 | undetected-chromedriver |
|---|---|---|
| GitHub stars | 95,849 | 12,914 |
| Forks | 9,607 | 1,344 |
| Open issues | 201 | 1,142 |
| Adoption | 100 | 82 |
| Activity | 100 | 16 |
| Community | 100 | 79 |
| Issue health | 96 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 63.5 |
JavaScript API for Chrome and Firefox
Custom Selenium Chromedriver | Zero-Config | Passes ALL bot mitigation systems (like Distil / Imperva/ Datadadome / CloudFlare IUAM)
puppeteer has more GitHub stars: 95,849 versus 12,914 for undetected-chromedriver. The gap is 82,935 stars.
puppeteer was pushed more recently: 17 November 2026 versus 05 July 2025 for undetected-chromedriver. That is 500 days apart.
Yes. This catalog marks both puppeteer and undetected-chromedriver 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. undetected-chromedriver is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and undetected-chromedriver scores 63.5. This page calls that a decisive lead for puppeteer.