A
openmeld
76.6
1,427 stars · MIT
Workflow Automation
puppeteer leads by 22.5 · decisive
A
76.6
1,427 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
openmeld versus puppeteer 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 76.6 for openmeld and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to openmeld's 1,427, a gap of 94,422 (67.17×). Forks are 89 for openmeld and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 63 versus 100, and the fork community is 49 versus 100.
Push history: openmeld was last pushed on 13 November 2026 (4 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 21 for openmeld (0.015 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 92 and 100.
openmeld 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. 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. License scores in this pair are 96 for openmeld and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both openmeld (1,427 stars) and puppeteer (95,849 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: openmeld is open source, puppeteer 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 51 points (49 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against openmeld at 76.6, a 22.5 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 | openmeld | puppeteer |
|---|---|---|
| GitHub stars | 1,427 | 95,849 |
| Forks | 89 | 9,607 |
| Open issues | 21 | 201 |
| Adoption | 63 | 100 |
| Activity | 92 | 100 |
| Community | 49 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 76.6 | 99.1 |
The open-source collaboration system for people and AI agents. Share context, coordinate tasks, and work in parallel with your team, cloud agents, Codex, Claude Code, Grok, Grok Bot, OpenCode, Antigravity, and Cursor.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 1,427 for openmeld. The gap is 94,422 stars.
puppeteer was pushed more recently: 17 November 2026 versus 13 November 2026 for openmeld. That is 4 days apart.
Yes. This catalog marks both openmeld and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
openmeld 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
puppeteer scores 99.1 and openmeld scores 76.6. This page calls that a decisive lead for puppeteer.