A · leads
puppeteer
99.1
95,849 stars · Apache-2.0
Workflow Automation
puppeteer leads by 20.0 · decisive
A · leads
99.1
95,849 stars · Apache-2.0
B
79.1
1,635 stars · Apache-2.0
puppeteer versus rulego 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; rulego is written mainly in Go. The composite score is 99.1 for puppeteer and 79.1 for rulego.
puppeteer has 95,849 GitHub stars to rulego's 1,635, a gap of 94,214 (58.62×). Forks are 9,607 for puppeteer and 164 for rulego. On the log scale used inside this pair, adoption is 100 versus 64, and the fork community is 100 versus 56.
Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and rulego was last pushed on 13 November 2026 (4 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 4 for rulego (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.
Both puppeteer and rulego are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both puppeteer (95,849 stars) and rulego (1,635 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, rulego 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 44 points (100 vs 56), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against rulego at 79.1, a 20.0 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 | rulego |
|---|---|---|
| GitHub stars | 95,849 | 1,635 |
| Forks | 9,607 | 164 |
| Open issues | 201 | 4 |
| Adoption | 100 | 64 |
| Activity | 100 | 92 |
| Community | 100 | 56 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.1 | 79.1 |
JavaScript API for Chrome and Firefox
⛓️RuleGo is a lightweight, high-performance, embedded, next-generation component orchestration rule engine framework for Go.
puppeteer has more GitHub stars: 95,849 versus 1,635 for rulego. The gap is 94,214 stars.
puppeteer was pushed more recently: 17 November 2026 versus 13 November 2026 for rulego. That is 4 days apart.
Yes. This catalog marks both puppeteer and rulego 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. rulego 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 rulego scores 79.1. This page calls that a decisive lead for puppeteer.