updated 2026-11-10 04:07 UTC

Camofox Browser

Repository

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

Browser & Computer Use JavaScript Listed MIT

Is Camofox Browser safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.4 / 10
Provenance Attested
Signed commits 8%
Last push 8d ago
Advisories None known
Compare Camofox Browser

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

Pick any agent to compare →
Suggest a correction

In detail: Camofox Browser scores 72.7/100 (Grade B), ranked #315 of 1374 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.4/10; 8% of recent commits are signed; no published advisory affects its latest release (@askjo/camofox-browser); last pushed 2026-11-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How Camofox Browser could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Camofox Browser and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/jo-inc/camofox-browser, MIT, last pushed 2026-11-02. 8% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.4/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 2
    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 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @askjo/camofox-browser 1.18.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 5.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Camofox Browser’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Camofox Browser compares in Browser & Computer Use

  1. #11 Browser Use 73.0 +0.3
  2. #12 Webcmd 72.8 +0.1
  3. #13 Camofox Browser 72.7 this agent
  4. #14 BrowserOS 66.5 −6.2
  5. #15 Obscura 65.3 −7.4

Bars show each HVTrust score; the tick marks Camofox Browser’s 72.7.

Where the 72.7 comes from

HVTrust dimensions vs the Browser & Computer Use average

72.7 / 100 · 100.0% confidence

Camofox Browser Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.4 / 25
3.1 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.3 above avg 12.7
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
11.5 / 20
0.5 below avg 12.0
AdoptionLog-scaled stars · package downloads
15.2 / 20
4.0 above avg 11.2

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-04
Rank Moved
Rank dropped 31 spots (#267 → #298)
2026-11-04
Activity Score Changed
Activity score down 11pts (74 → 64)
2026-11-03
Rank Moved
Rank dropped 29 spots (#238 → #267)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/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.
Compare with another agent
View Browser & Computer Use Report missing data
62.8
Activity sub-score · out of 100
#13
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 8 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
12.2k
Forks
1.2k
Last Push
2026-11-02
8 days ago
Commits (4 wk)
0
Downloads (7d)
11,343
npm
HN mentions (30d)
—
Open Issues
114
Rank Change
▲3
was #318

Analysis

Activity Inputs

62.8 / 100
StarsRepository reach
24.5 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
14.4 / 20

Common questions about Camofox Browser

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?
Camofox Browser has an OpenSSF Scorecard score of 4.4/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?
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?
8% 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-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Provenance Added
Package provenance attestation detected
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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 18Grade 7HVTrust 4Score 3Surface 2Scorecard 1Surface 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-04
Rank Moved
Rank dropped 31 spots (#267 → #298)
2026-11-04
Activity Score Changed
Activity score down 11pts (74 → 64)
2026-11-03
Rank Moved
Rank dropped 29 spots (#238 → #267)
2026-11-01
Rank Moved
Rank dropped 22 spots (#223 → #245)
2026-10-30
Rank Moved
Rank dropped 27 spots (#190 → #217)
2026-10-30
Activity Score Changed
Activity score down 5pts (81 → 76)
2026-10-20
Grade Changed
Trust grade A → B
2026-10-09
Rank Moved
Rank dropped 12 spots (#118 → #130)
2026-10-06
Rank Moved
Rank dropped 11 spots (#105 → #116)
2026-10-01
Rank Moved
Rank rose 13 spots (#121 → #108)
2026-09-30
Rank Moved
Rank rose 11 spots (#132 → #121)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → A
2026-09-23
Rank Moved
Rank rose 496 spots (#619 → #123)
2026-09-23
HVTrust Changed
HVTrust up 48.9pts (33.2 → 82.1)
2026-09-22
Newly Listed
First tracked at rank #619
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-10
Grade Changed
Trust grade B → A
2026-09-10
Rank Moved
Rank rose 30 spots (#138 → #108)
2026-09-10
Activity Score Changed
Activity score up 7pts (79 → 86)
2026-09-08
Grade Changed
Trust grade A → B
2026-09-08
Rank Moved
Rank dropped 16 spots (#125 → #141)
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 654 spots (#771 → #117)
2026-09-05
HVTrust Changed
HVTrust up 30.4pts (50.4 → 80.8)
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)
GitHub → npm: @askjo/camofox-browser

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 72.7 Grade B
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.4 · Raw JSON