Is Camofox Browser safe to use?

Camofox Browser has an HVTrust score of 71.9/100 (Grade B), ranked #121 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Camofox Browser?

Camofox Browser scores 71.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 8.5k GitHub stars and is categorized under Browser & Computer Use.

Camofox Browser

jo-inc/camofox-browser

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

Browser & Computer Use JavaScript Grade B Listed MIT

71.9/100

Rank #121 of 1283

Compare Camofox Browser

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-04 · 8d ago

Recent change

New

Is Camofox Browser safe? Camofox Browser scores 71.9/100 (Grade B), ranked #121 of 1283 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; no OSSF Scorecard result yet; 24% of recent commits are signed; last pushed 2026-08-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#7 Cua — 74.2 (B) → #8 Browser Use — 73.7 (B) → #10 Browser4 — 66.6 (B) → #11 OpenCLI — 64.6 (C) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-10

Newly Listed

First tracked at rank #116

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Camofox Browser View Browser & Computer Use Report missing data

84.2

Activity sub-score · out of 100

In Browser & Computer Use

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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

2026-08-11 2026-08-12

Activity & Reach

Stars

8.5k

Forks

899

Last Push

2026-08-04

8 days ago

Commits (4 wk)

Downloads (7d)

60,042

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #120

Analysis

HVTrust Dimensions vs Browser & Computer Use

71.9 / 100 · 100.0% confidence

Camofox Browser Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.7 / 25

1.3 above avg 7.4

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.6 above avg 12.4

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

2.3 below avg 10.8

Maintenance60% last-push freshness · 40% commit activity

18.8 / 20

5.8 above avg 13.0

AdoptionLog-scaled stars · package downloads

15.8 / 20

4.6 above avg 11.2

Activity Inputs

84.2 / 100

StarsRepository reach

23.6 / 30

FreshnessLast push recency

23.9 / 25

ActivityRecent commits

23.0 / 25

CommunityFork signal

13.7 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

24%

of last 100 commits verified

Is Camofox Browser safe?

Camofox Browser has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

No OpenSSF Scorecard data is currently published for Camofox Browser. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is Camofox Browser actively maintained?

Maintained. Last push was 8 days ago.

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?

24% 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

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Extensions

Extension based 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

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-10

Newly Listed

First tracked at rank #116

GitHub → npm: @askjo/camofox-browser

Embed Badge Badge guide for maintainers →

For maintainers

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON