jo-inc/camofox-browser
Infrastructure · tested 2026-07-23 · by the Hlido desk, not the vendor
In short: A well-engineered MIT stealth browser that drops into Puppeteer/Playwright for agent scraping — strong hygiene and traction, but its whole purpose (bypassing bot detection) is a compliance and ToS minefield.
10 PASS · 0 FAIL of 10 public-surface claims
Quick answer
jo-inc/camofox-browser scores 82/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-07-23). STEADY (82, the repo-surface ceiling). Pricing: Open source (free entry point documented).
On pure repository signals this is one of the healthier projects in its category: MIT-licensed, 7.7k stars, six CI workflows, a frequent release cadence (v1.11.2) and a large 34k-char README. Drop-in API compatibility with Puppeteer/Playwright makes adoption cheap for agents already on those stacks. The honest caveat isn't technical — it's what the tool is for. Its stated purpose is to defeat Cloudflare, bot detection and anti-scraping, so any agent that uses it inherits the target site's Terms of Service and, in some jurisdictions, computer-access law. That makes it a capability to deploy deliberately against cooperating or owned targets, not a default dependency. The 178 open issues are worth watching against the release cadence. Repo-surface read; stealth effectiveness is an arms race we can't verify from the repo.
Why STEADY
STEADY (82, the repo-surface ceiling). MIT licensing, strong CI hygiene, frequent releases, drop-in compatibility and heavy traction all clear STEADY. VITAL is withheld because effectiveness against evolving detectors cannot be verified from repo signals, and the compliance profile is inherently caller-dependent.
Public-surface checklist
- PASS Repo reachable (required) — GH API 200 for jo-inc/camofox-browser
- PASS Readme present (required) — README length 34863
- PASS License present (required) — MIT
- PASS Install documented (required) — install/usage section found in README
- PASS Active 12mo (required) — last push 30d ago
- PASS Releases present — latest v1.11.2
- PASS Community traction — 7733 stars
- PASS Ci or tests — 6 workflow file(s)
- PASS Recent commit 90d — last push 30d ago
- PASS Agent consumable — CLI install line in README
What we saw
1 screenshot captured by the Hlido engine during the reviewed run (run-b0d79ae89fbec80e-github-com). Our own captures — not vendor marketing material.
What it does well
- MIT-licensed and drop-in compatible with Puppeteer/Playwright — low adoption cost
- Unusually strong engineering hygiene for the category (6 CI workflows)
- Frequent tagged releases (v1.11.2) and active maintenance (push within ~30 days)
- Large, detailed README (~34.9k chars); solid traction (7.7k stars)
What it fails at
- 178 open issues — a sizable backlog to weigh against the release cadence
- Stealth effectiveness is unverifiable from the repo surface (an arms race vs. detectors)
- No guarantee against future breakage as anti-bot systems evolve
Red flags
- [object Object]
Best for
- Agents needing resilient headless browsing against cooperating or owned targets
- Teams already on Puppeteer/Playwright wanting a drop-in replacement
Not recommended for
- Use against sites whose Terms of Service forbid automated access
- Compliance-sensitive organizations
- Anyone needing a stable, non-arms-race dependency
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-07-16.
Related agents
Agent relevance
API CLI SDK
Agentic-Commerce Readiness 46/100 · SURFACE-ONLY
Independent readiness for agent delegation & transaction. How it’s scored · check live
Drop-in Puppeteer/Playwright-compatible library an agent can call directly for headless browsing; installed via the documented CLI/package line. No hands-on behavioral test performed.
Agent-friendly score: 7/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
