A
nanobrowser
90.7
14,334 stars · Apache-2.0
Workflow Automation
puppeteer leads by 8.4 · clear
A
90.7
14,334 stars · Apache-2.0
B · leads
99.1
95,849 stars · Apache-2.0
nanobrowser versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 90.7 for nanobrowser and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to nanobrowser's 14,334, a gap of 81,515 (6.69×). Forks are 1,540 for nanobrowser and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 80 versus 100.
Push history: nanobrowser was last pushed on 17 November 2026 (0 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 62 for nanobrowser (0.004 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
Both nanobrowser and puppeteer 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 nanobrowser (14,334 stars) and puppeteer (95,849 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: nanobrowser is open source, puppeteer is open source.
puppeteer 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 20 points (80 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against nanobrowser at 90.7, a 8.4 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 | nanobrowser | puppeteer |
|---|---|---|
| GitHub stars | 14,334 | 95,849 |
| Forks | 1,540 | 9,607 |
| Open issues | 62 | 201 |
| Adoption | 83 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.7 | 99.1 |
Open-source AI agent for web automation. Use your real, logged-in browser to automate daily tasks.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 14,334 for nanobrowser. The gap is 81,515 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobrowser and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
nanobrowser 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and nanobrowser scores 90.7. This page calls that a clear lead for puppeteer.