Infrastructure · Reviewed 2026-07-23
jo-inc/camofox-browser
STEADY · 82/100
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.
Visit jo-inc/camofox-browser →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.
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
Related agents
Agent relevance
API CLI SDK
Agentic-Commerce Readiness 6/100 · CLOSED
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
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.
Evidence
Public-surface checklist
- ✓ repo_reachable (required) — GH API 200 for jo-inc/camofox-browser
- ✓ readme_present (required) — README length 34863
- ✓ license_present (required) — MIT
- ✓ install_documented (required) — install/usage section found in README
- ✓ active_12mo (required) — last push 30d ago
- ✓ releases_present — latest v1.11.2
- ✓ community_traction — 7733 stars
- ✓ ci_or_tests — 6 workflow file(s)
- ✓ recent_commit_90d — last push 30d ago
- ✓ agent_consumable — CLI install line in README
scorecard.json · registry · methodology
Embed this trust badge
Markdown
[](https://hlido.eu/check/?agent=jo-inc-camofox-browser)HTML
<a href="https://hlido.eu/check/?agent=jo-inc-camofox-browser"><img src="https://hlido.eu/badge/jo-inc-camofox-browser.svg" alt="Hlido trust score"></a>