A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 12.5 · clear
A · leads
99.1
95,849 stars · Apache-2.0
B
86.6
11,990 stars · Apache-2.0
puppeteer versus robotframework 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; robotframework is written mainly in Python. The composite score is 99.1 for puppeteer and 86.6 for robotframework.
puppeteer has 95,849 GitHub stars to robotframework's 11,990, a gap of 83,859 (7.99×). Forks are 9,607 for puppeteer and 2,589 for robotframework. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 86.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and robotframework was last pushed on 11 November 2026 (6 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 322 for robotframework (0.027 per star). Issue-health scores are 96 and 70; activity scores are 100 and 92.
Both puppeteer and robotframework 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 puppeteer (95,849 stars) and robotframework (11,990 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, robotframework is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against robotframework at 86.6, a 12.5 point clear 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 | robotframework |
|---|---|---|
| GitHub stars | 95,849 | 11,990 |
| Forks | 9,607 | 2,589 |
| Open issues | 201 | 322 |
| Adoption | 100 | 82 |
| Activity | 100 | 92 |
| Community | 100 | 86 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 86.6 |
JavaScript API for Chrome and Firefox
Generic automation framework for acceptance testing and RPA
puppeteer has more GitHub stars: 95,849 versus 11,990 for robotframework. The gap is 83,859 stars.
puppeteer was pushed more recently: 17 November 2026 versus 11 November 2026 for robotframework. That is 6 days apart.
Yes. This catalog marks both puppeteer and robotframework 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. robotframework 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.
puppeteer scores 99.1 and robotframework scores 86.6. This page calls that a clear lead for puppeteer.