updated 2026-10-13 04:10 UTC

Browser Harness

Repository Website by browser-use

Browser Harness | Self-healing harness that enables LLMs to complete any task.

Browser & Computer Use Python Listed MIT

Is Browser Harness safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.9 / 10
Provenance Attested
Signed commits 31%
Last push today
Advisories None known
Compare Browser Harness

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

Pick any agent to compare →
Suggest a correction

In detail: Browser Harness scores 90.2/100 (Grade A), ranked #21 of 1371 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 5.9/10; 31% of recent commits are signed; no published advisory affects its latest release (browser-harness); last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Browser Harness 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 Browser Harness 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/browser-use/browser-harness, MIT, last pushed 2026-10-13. 31% 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 5.9/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:

    • Code Review8
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 1
    CII-Best-Practices 0
    Code-Review 8
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 10

  3. Published packages Linked and attested

    • PyPI browser-harness Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: browser-harness 0.1.13. No published advisory affects it (OSV, checked 2026-10-13).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Browser Harness.

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 Browser Harness’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 Browser Harness compares in Browser & Computer Use

  1. #1 agent-device 91.6 +1.4
  2. #2 OpenClaw 90.4 +0.2
  3. #3 Browser Harness 90.2 this agent
  4. #4 Peekaboo 89.9 −0.3
  5. #5 Stagehand 89.0 −1.2

Bars show each HVTrust score; the tick marks Browser Harness’s 90.2.

Where the 90.2 comes from

HVTrust dimensions vs the Browser & Computer Use average

90.2 / 100 · 100.0% confidence

Browser Harness Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
16.4 / 25
6.4 above avg 10.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.3 above avg 12.7
Transparency50% declared license · 50% OSSF Scorecard
13.5 / 17
1.6 above avg 11.9
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.2 above avg 12.8
AdoptionLog-scaled stars · package downloads
18.5 / 20
7.3 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-10-09
Rank Moved
Rank rose 81 spots (#99 → #18)
2026-10-09
HVTrust Changed
HVTrust up 6.5pts (84.2 → 90.7)
2026-10-09
Activity Score Changed
Activity score up 26pts (64 → 91)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.9/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 agent-device Get email alerts for Browser Harness View Browser & Computer Use Report missing data
90.7
Activity sub-score · out of 100
#3
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 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 →

Signals refreshed 2026-10-13 04:10 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-13

Activity & Reach

Stars
18.4k
Forks
1.8k
Last Push
2026-10-13
today
Commits (4 wk)
100
Downloads (7d)
1,482,196
pypi
HN mentions (30d)
—
Open Issues
54
Rank Change
▼1
was #20

Analysis

Activity Inputs

90.7 / 100
StarsRepository reach
25.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.1 / 20

Common questions about Browser Harness

Public supply-chain signals for Browser Harness are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Browser Harness carries less obvious unverified-evidence risk than projects with thin signals.
Does Browser Harness publish package provenance?
Yes. Browser Harness's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Browser Harness have an OpenSSF Scorecard?
Browser Harness has an OpenSSF Scorecard score of 5.9/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 Browser Harness actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Browser Harness use?
Browser Harness ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Browser Harness's commits signed?
31% of the last 100 commits to Browser Harness 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.

Compare Browser Harness head-to-head

Browser Harness vs agent-device → Browser Harness vs OpenClaw → Browser Harness vs Peekaboo →

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
high confidence
Implemented
Browser Harness appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
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 Browser Harness'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-08-29
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic

Maintain Browser Harness?

For maintainers

HVTrust scores Browser Harness 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 5Score 3Surface 1MCP 1HVTrust 1
2026-10-09
Rank Moved
Rank rose 81 spots (#99 → #18)
2026-10-09
HVTrust Changed
HVTrust up 6.5pts (84.2 → 90.7)
2026-10-09
Activity Score Changed
Activity score up 26pts (64 → 91)
2026-10-08
Rank Moved
Rank dropped 20 spots (#79 → #99)
2026-10-07
Rank Moved
Rank dropped 18 spots (#61 → #79)
2026-10-07
Activity Score Changed
Activity score down 5pts (73 → 68)
2026-10-06
Rank Moved
Rank rose 13 spots (#74 → #61)
2026-10-05
Rank Moved
Rank dropped 35 spots (#39 → #74)
2026-10-05
Activity Score Changed
Activity score down 5pts (79 → 73)
2026-08-29
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
GitHub → Website → PyPI: browser-harness

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 90.2 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/browser-harness.svg)](https://hvtracker.net/agents/browser-harness)
HTML:
<a href="https://hvtracker.net/agents/browser-harness"><img src="https://hvtracker.net/badge/browser-harness.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON