A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 11.6 · clear
A · leads
99.1
95,849 stars · Apache-2.0
B
87.5
9,166 stars · MIT
puppeteer versus rig 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; rig is written mainly in Rust. The composite score is 99.1 for puppeteer and 87.5 for rig.
puppeteer has 95,849 GitHub stars to rig's 9,166, a gap of 86,683 (10.46×). Forks are 9,607 for puppeteer and 1,023 for rig. On the log scale used inside this pair, adoption is 100 versus 80, and the fork community is 100 versus 76.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and rig was last pushed on 17 November 2026 (0 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 64 for rig (0.007 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. rig 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 rig. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and rig (9,166 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, rig is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 24 points (100 vs 76), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against rig at 87.5, a 11.6 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 | puppeteer | rig |
|---|---|---|
| GitHub stars | 95,849 | 9,166 |
| Forks | 9,607 | 1,023 |
| Open issues | 201 | 64 |
| Adoption | 100 | 80 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 87.5 |
JavaScript API for Chrome and Firefox
⚙️🦀 Build modular and scalable LLM Applications in Rust
puppeteer has more GitHub stars: 95,849 versus 9,166 for rig. The gap is 86,683 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both puppeteer and rig 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. rig 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 rig scores 87.5. This page calls that a clear lead for puppeteer.