A · leads
playwright
99.1
100,414 stars · Apache-2.0
Workflow Automation
playwright leads by 12.5 · clear
A · leads
99.1
100,414 stars · Apache-2.0
B
86.6
23,434 stars · AGPL-3.0
playwright versus skyvern 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; skyvern is written mainly in Python. The composite score is 99.1 for playwright and 86.6 for skyvern.
playwright has 100,414 GitHub stars to skyvern's 23,434, a gap of 76,980 (4.28×). Forks are 6,908 for playwright and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 87.
Push history: playwright was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 76 for playwright (0.001 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for playwright and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both playwright (100,414 stars) and skyvern (23,434 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, skyvern is open source.
playwright is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
playwright finishes ahead at 99.1 against skyvern 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 | playwright | skyvern |
|---|---|---|
| GitHub stars | 100,414 | 23,434 |
| Forks | 6,908 | 2,246 |
| Open issues | 76 | 301 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 86.6 |
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
Automate browser based workflows with AI
playwright has more GitHub stars: 100,414 versus 23,434 for skyvern. The gap is 76,980 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both playwright and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
playwright scores 99.1 and skyvern scores 86.6. This page calls that a clear lead for playwright.