A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 33.0 · decisive
A · leads
99.1
95,849 stars · Apache-2.0
B
66.1
1,415 stars · BSD-3-Clause
puppeteer versus utask 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; utask is written mainly in Go. The composite score is 99.1 for puppeteer and 66.1 for utask.
puppeteer has 95,849 GitHub stars to utask's 1,415, a gap of 94,434 (67.74×). Forks are 9,607 for puppeteer and 105 for utask. On the log scale used inside this pair, adoption is 100 versus 63, and the fork community is 100 versus 51.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and utask was last pushed on 29 July 2026 (111 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 85 for utask (0.060 per star). Issue-health scores are 96 and 52; activity scores are 100 and 58.
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. utask is listed as BSD-3-Clause, 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 puppeteer and 96 for utask. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and utask (1,415 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, utask is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 49 points (100 vs 51), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against utask at 66.1, a 33.0 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 | utask |
|---|---|---|
| GitHub stars | 95,849 | 1,415 |
| Forks | 9,607 | 105 |
| Open issues | 201 | 85 |
| Adoption | 100 | 63 |
| Activity | 100 | 58 |
| Community | 100 | 51 |
| Issue health | 96 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 66.1 |
JavaScript API for Chrome and Firefox
µTask is an automation engine that models and executes business processes declared in yaml. ✏️📋
puppeteer has more GitHub stars: 95,849 versus 1,415 for utask. The gap is 94,434 stars.
puppeteer was pushed more recently: 17 November 2026 versus 29 July 2026 for utask. That is 111 days apart.
Yes. This catalog marks both puppeteer and utask 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. utask is listed as BSD-3-Clause, 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 utask scores 66.1. This page calls that a decisive lead for puppeteer.