A
LoopForge
71.7
2,919 stars · license n/a
Workflow Automation
puppeteer leads by 27.4 · decisive
A
71.7
2,919 stars · license n/a
B · leads
99.1
95,849 stars · Apache-2.0
LoopForge versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. LoopForge is written mainly in Go; puppeteer is written mainly in TypeScript. The composite score is 71.7 for LoopForge and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to LoopForge's 2,919, a gap of 92,930 (32.84×). Forks are 423 for LoopForge and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 70 versus 100, and the fork community is 66 versus 100.
Push history: LoopForge was last pushed on 17 November 2026 (0 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 176 for LoopForge (0.060 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for LoopForge and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both LoopForge (2,919 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: LoopForge is unpriced in this catalog, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against LoopForge at 71.7, a 27.4 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 | LoopForge | puppeteer |
|---|---|---|
| GitHub stars | 2,919 | 95,849 |
| Forks | 423 | 9,607 |
| Open issues | 176 | 201 |
| Adoption | 70 | 100 |
| Activity | 100 | 100 |
| Community | 66 | 100 |
| Issue health | 52 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 71.7 | 99.1 |
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 2,919 for LoopForge. The gap is 92,930 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both LoopForge and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 LoopForge scores 71.7. This page calls that a decisive lead for puppeteer.