A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 32.7 · decisive
A · leads
99.1
95,849 stars · Apache-2.0
B
66.4
10,062 stars · LGPL-3.0
puppeteer versus tpot 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; tpot is written mainly in Jupyter Notebook. The composite score is 99.1 for puppeteer and 66.4 for tpot.
puppeteer has 95,849 GitHub stars to tpot's 10,062, a gap of 85,787 (9.53×). Forks are 9,607 for puppeteer and 1,557 for tpot. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 80.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and tpot was last pushed on 11 September 2025 (431 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 312 for tpot (0.031 per star). Issue-health scores are 96 and 70; 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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for puppeteer and 78 for tpot. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and tpot (10,062 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, tpot 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 tpot at 66.4, a 32.7 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 | tpot |
|---|---|---|
| GitHub stars | 95,849 | 10,062 |
| Forks | 9,607 | 1,557 |
| Open issues | 201 | 312 |
| Adoption | 100 | 80 |
| Activity | 100 | 16 |
| Community | 100 | 80 |
| Issue health | 96 | 70 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 66.4 |
JavaScript API for Chrome and Firefox
A Python Automated Machine Learning tool that optimizes machine learning pipelines using genetic programming.
puppeteer has more GitHub stars: 95,849 versus 10,062 for tpot. The gap is 85,787 stars.
puppeteer was pushed more recently: 17 November 2026 versus 11 September 2025 for tpot. That is 431 days apart.
Yes. This catalog marks both puppeteer and tpot 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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and tpot scores 66.4. This page calls that a decisive lead for puppeteer.