A · leads
playwright
99.1
100,414 stars · Apache-2.0
Workflow Automation
playwright leads by 32.8 · decisive
A · leads
99.1
100,414 stars · Apache-2.0
B
66.3
1,415 stars · BSD-3-Clause
playwright versus utask is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. playwright is written mainly in TypeScript; utask is written mainly in Go. The composite score is 99.1 for playwright and 66.3 for utask.
playwright has 100,414 GitHub stars to utask's 1,415, a gap of 98,999 (70.96×). Forks are 6,908 for playwright and 105 for utask. On the log scale used inside this pair, adoption is 100 versus 63, and the fork community is 100 versus 53.
Push history: playwright 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 76 for playwright (0.001 per star) and 85 for utask (0.060 per star). Issue-health scores are 96 and 52; activity scores are 100 and 58.
playwright 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 playwright and 96 for utask. This is a procurement signal, not legal advice.
In Workflow Automation, both playwright (100,414 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: playwright is open source, utask is open source.
playwright is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 47 points (100 vs 53), and the tightest is self-hosting at 0 points (100 vs 100).
playwright finishes ahead at 99.1 against utask at 66.3, a 32.8 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 | playwright | utask |
|---|---|---|
| GitHub stars | 100,414 | 1,415 |
| Forks | 6,908 | 105 |
| Open issues | 76 | 85 |
| Adoption | 100 | 63 |
| Activity | 100 | 58 |
| Community | 100 | 53 |
| Issue health | 96 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 66.3 |
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
µTask is an automation engine that models and executes business processes declared in yaml. ✏️📋
playwright has more GitHub stars: 100,414 versus 1,415 for utask. The gap is 98,999 stars.
playwright was pushed more recently: 17 November 2026 versus 29 July 2026 for utask. That is 111 days apart.
Yes. This catalog marks both playwright and utask as self-hostable. Confirm each project's deploy docs before you plan a migration.
playwright 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.
playwright scores 99.1 and utask scores 66.3. This page calls that a decisive lead for playwright.