A
paperclip
94.7
114,484 stars · MIT
Workflow Automation
playwright leads by 2.6 · narrow
A
94.7
114,484 stars · MIT
B · leads
97.3
100,414 stars · Apache-2.0
paperclip versus playwright 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 94.7 for paperclip and 97.3 for playwright.
paperclip has 114,484 GitHub stars to playwright's 100,414, a gap of 14,070 (1.14×). Forks are 18,987 for paperclip and 6,908 for playwright. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 90.
Push history: paperclip was last pushed on 17 November 2026 (0 days ago), and playwright was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6,806 for paperclip (0.059 per star) and 76 for playwright (0.001 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
paperclip 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. 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. License scores in this pair are 96 for paperclip and 96 for playwright. This is a procurement signal, not legal advice.
In Workflow Automation, both paperclip (114,484 stars) and playwright (100,414 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: paperclip is open source, playwright is open source.
The lead is split. paperclip is furthest ahead on fork community (100 to 90), while playwright is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
playwright finishes ahead at 97.3 against paperclip at 94.7, a 2.6 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 | paperclip | playwright |
|---|---|---|
| GitHub stars | 114,484 | 100,414 |
| Forks | 18,987 | 6,908 |
| Open issues | 6,806 | 76 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 97.3 |
The open-source app everyone uses to manage agents at work
Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
paperclip has more GitHub stars: 114,484 versus 100,414 for playwright. The gap is 14,070 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both paperclip and playwright as self-hostable. Confirm each project's deploy docs before you plan a migration.
paperclip 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
playwright scores 97.3 and paperclip scores 94.7. This page calls that a narrow lead for playwright.