A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 17.8 · decisive
A · leads
99.1
95,849 stars · Apache-2.0
B
81.3
2,735 stars · MIT
puppeteer versus yao-meta-skill 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; yao-meta-skill is written mainly in Python. The composite score is 99.1 for puppeteer and 81.3 for yao-meta-skill.
puppeteer has 95,849 GitHub stars to yao-meta-skill's 2,735, a gap of 93,114 (35.05×). Forks are 9,607 for puppeteer and 254 for yao-meta-skill. On the log scale used inside this pair, adoption is 100 versus 69, and the fork community is 100 versus 60.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and yao-meta-skill was last pushed on 09 November 2026 (8 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 3 for yao-meta-skill (0.001 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.
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. yao-meta-skill 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. License scores in this pair are 96 for puppeteer and 96 for yao-meta-skill. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and yao-meta-skill (2,735 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, yao-meta-skill is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 40 points (100 vs 60), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against yao-meta-skill at 81.3, a 17.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 | puppeteer | yao-meta-skill |
|---|---|---|
| GitHub stars | 95,849 | 2,735 |
| Forks | 9,607 | 254 |
| Open issues | 201 | 3 |
| Adoption | 100 | 69 |
| Activity | 100 | 92 |
| Community | 100 | 60 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 81.3 |
JavaScript API for Chrome and Firefox
YAO = Yielding AI Outcomes. A rigorous engineering, evaluation, governance, and portability system for reusable agent skills.
puppeteer has more GitHub stars: 95,849 versus 2,735 for yao-meta-skill. The gap is 93,114 stars.
puppeteer was pushed more recently: 17 November 2026 versus 09 November 2026 for yao-meta-skill. That is 8 days apart.
Yes. This catalog marks both puppeteer and yao-meta-skill 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. yao-meta-skill 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and yao-meta-skill scores 81.3. This page calls that a decisive lead for puppeteer.