Camofox Browser
Stealth headless browser for AI agents — bypass Cloudflare, bot detection, and anti-scraping. Drop-in Puppeteer/Playwright replacement.
Is Camofox Browser safe? Strong public trust posture, backed by multiple independent signals.
Compare Camofox Browser
How does it stack up against its Browser & Computer Use neighbours?
Pick any agent to compare →In detail: Camofox Browser scores 81.7/100 (Grade A), ranked #128 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.9/10; 3% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How Camofox Browser compares in Browser & Computer Use
- #5 Agent Browser 87.7 +6.0
- #6 Skyvern 86.9 +5.2
- #7 Camofox Browser 81.7 this agent
- #8 agent-device 80.1 −1.6
- #9 Peekaboo 76.9 −4.8
Bars show each HVTrust score; the tick marks Camofox Browser’s 81.7.
Where the 81.7 comes from
HVTrust dimensions vs the Browser & Computer Use average
81.7 / 100 · 100.0% confidenceCamofox Browser Browser & Computer Use average (42 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
86.2 / 100Supply Chain Trust
Common questions about Camofox Browser
Does Camofox Browser publish package provenance?
Does Camofox Browser have an OpenSSF Scorecard?
Is Camofox Browser actively maintained?
What license does Camofox Browser use?
Are Camofox Browser's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Compare Camofox Browser head-to-head
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- browser
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Camofox Browser's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Camofox Browser?
For maintainers
HVTrust scores Camofox Browser from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/camofox-browser)
<a href="https://hvtracker.net/agents/camofox-browser"><img src="https://hvtracker.net/badge/camofox-browser.svg" alt="HVTrust"></a>
Other agents in Browser & Computer Use
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON