Camofox Browser

Stealth headless browser for AI agents — bypass Cloudflare, bot detection, and anti-scraping. Drop-in Puppeteer/Playwrig

Browser & Computer Use JavaScript Grade C Listed MIT
50.4/100
Rank #771 of 1320
Compare Camofox Browser

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-03 · 1d ago
Recent change
Rank +8

Is Camofox Browser safe? Camofox Browser scores 50.4/100 (Grade C), ranked #771 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.0/10; 19% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 30 spots (#741 → #771)
2026-09-03
Rank Moved
Rank dropped 40 spots (#701 → #741)
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
78.4
Activity sub-score · out of 100
#24

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 23:12 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
9.1k
Forks
971
Last Push
2026-09-03
yesterday
Commits (4 wk)
18
Downloads (7d)
HN mentions (30d)
Open Issues
78
Rank Change
▼30
was #741

Analysis

HVTrust Dimensions vs Browser & Computer Use

50.4 / 100 · 67.0% confidence

Camofox Browser Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.7 / 25
5.4 above avg 9.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.6 above avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
1.1 above avg 11.7
Maintenance60% last-push freshness · 40% commit activity
17.0 / 20
4.0 above avg 13.0
AdoptionLog-scaled stars · package downloads
9.5 / 20
0.9 below avg 10.4

Activity Inputs

78.4 / 100
StarsRepository reach
23.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
15.9 / 25
CommunityFork signal
13.9 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Sep 2, 2026
Signed Commits
19%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 3
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 10

Is Camofox Browser safe?

Public trust evidence for Camofox Browser is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Camofox Browser publish package provenance?
Yes. Camofox Browser's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Camofox Browser have an OpenSSF Scorecard?
Camofox Browser has an OpenSSF Scorecard score of 5.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Camofox Browser actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Camofox Browser use?
Camofox Browser ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Camofox Browser's commits signed?
19% of the last 100 commits to Camofox Browser are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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 →

MCP Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-09-02
Provider Removed
Runtime surface shrank — no longer detected: Anthropic

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
Rank 6HVTrust 2Grade 2Listed 1Scorecard 1Surface 1Surface 1
2026-09-04
Rank Moved
Rank dropped 30 spots (#741 → #771)
2026-09-03
Rank Moved
Rank dropped 40 spots (#701 → #741)
2026-09-02
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-09-02
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-09-02
Grade Changed
Trust grade A → C
2026-09-02
Rank Moved
Rank dropped 604 spots (#97 → #701)
2026-09-02
HVTrust Changed
HVTrust down 30.3pts (80.4 → 50.1)
2026-09-01
Rank Moved
Rank dropped 16 spots (#81 → #97)
2026-08-31
Rank Moved
Rank dropped 12 spots (#69 → #81)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.0/10
2026-08-26
Grade Changed
Trust grade B → A
2026-08-26
Rank Moved
Rank rose 61 spots (#127 → #66)
2026-08-26
HVTrust Changed
HVTrust up 10.5pts (71.8 → 82.3)
2026-08-10
Newly Listed
First tracked at rank #116

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/camofox-browser.svg)](https://hvtracker.net/agents/camofox-browser)
HTML:
<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

Data sources
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