A
nanobot
95.9
50,147 stars · MIT
Workflow Automation
puppeteer leads by 3.2 · narrow
A
95.9
50,147 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
nanobot versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. nanobot is written mainly in Python; puppeteer is written mainly in TypeScript. The composite score is 95.9 for nanobot and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to nanobot's 50,147, a gap of 45,702 (1.91×). Forks are 8,755 for nanobot and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 99 versus 100.
Push history: nanobot 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 872 for nanobot (0.017 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
nanobot is listed as MIT, 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. License scores in this pair are 96 for nanobot and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 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: nanobot is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 12 points (84 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against nanobot at 95.9, a 3.2 point narrow 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 | nanobot | puppeteer |
|---|---|---|
| GitHub stars | 50,147 | 95,849 |
| Forks | 8,755 | 9,607 |
| Open issues | 872 | 201 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 95.9 | 99.1 |
Your lightweight open-source personal agent.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 50,147 for nanobot. The gap is 45,702 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
nanobot is listed as MIT, 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 nanobot scores 95.9. This page calls that a narrow lead for puppeteer.