A
camofox-browser
87.0
12,352 stars · MIT
Workflow Automation
puppeteer leads by 12.1 · clear
A
87.0
12,352 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
camofox-browser versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. camofox-browser is written mainly in JavaScript; puppeteer is written mainly in TypeScript. The composite score is 87.0 for camofox-browser and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to camofox-browser's 12,352, a gap of 83,497 (7.76×). Forks are 1,247 for camofox-browser and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 78 versus 100.
Push history: camofox-browser was last pushed on 10 November 2026 (7 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 70 for camofox-browser (0.006 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 92 and 100.
camofox-browser 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 camofox-browser and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both camofox-browser (12,352 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: camofox-browser 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 22 points (78 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against camofox-browser at 87.0, a 12.1 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 | camofox-browser | puppeteer |
|---|---|---|
| GitHub stars | 12,352 | 95,849 |
| Forks | 1,247 | 9,607 |
| Open issues | 70 | 201 |
| Adoption | 82 | 100 |
| Activity | 92 | 100 |
| Community | 78 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.0 | 99.1 |
Stealth headless browser for AI agents — bypass Cloudflare, bot detection, and anti-scraping. Drop-in Puppeteer/Playwright replacement.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 12,352 for camofox-browser. The gap is 83,497 stars.
puppeteer was pushed more recently: 17 November 2026 versus 10 November 2026 for camofox-browser. That is 7 days apart.
Yes. This catalog marks both camofox-browser and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
camofox-browser 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 camofox-browser scores 87.0. This page calls that a clear lead for puppeteer.