Is Browser Harness safe to use?

Browser Harness has an HVTrust score of 88.1/100 (Grade A), ranked #21 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Browser Harness?

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

Browser Harness

browser-use/browser-harness

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

Browser & Computer Use Python Grade A Listed MIT

88.1/100

Rank #21 of 1204

Compare Browser Harness

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

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-03 · 6d ago

Recent change

No recent signal change

Is Browser Harness safe? Browser Harness scores 88.1/100 (Grade A), ranked #21 of 1204 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 6.1/10; 39% of recent commits are signed; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#2 Agent Browser — 86.9 (A) → #3 OpenClaw — 86.5 (A) → #4 Stagehand — 84.7 (A) → #5 Skyvern — 81.5 (A) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-07-15

Scorecard Added

OSSF Scorecard: 5.3/10

2026-07-15

Grade Changed

Trust grade D → A

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.1/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 Browser Get email alerts for Browser Harness View Browser & Computer Use Report missing data

84.5

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 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 →

Activity & Reach

Stars

16.6k

Forks

1.6k

Last Push

2026-08-03

6 days ago

Commits (4 wk)

Downloads (7d)

2,493,083

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #22

Analysis

HVTrust Dimensions vs Browser & Computer Use

88.1 / 100 · 100.0% confidence

Browser Harness Browser & Computer Use average (34 agents)

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

17.1 / 25

9.4 above avg 7.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.9 above avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

13.7 / 17

2.5 above avg 11.2

Maintenance60% last-push freshness · 40% commit activity

18.0 / 20

6.0 above avg 12.0

AdoptionLog-scaled stars · package downloads

18.7 / 20

7.9 above avg 10.8

Activity Inputs

84.5 / 100

StarsRepository reach

25.3 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

20.0 / 25

CommunityFork signal

14.9 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

6.1 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

39%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 10

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 10

Is Browser Harness safe?

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 6.1/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 6 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?

39% 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 Browser → Browser Harness vs OpenClaw → Browser Harness vs Stagehand →

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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-07-15

Scorecard Added

OSSF Scorecard: 5.3/10

2026-07-15

Grade Changed

Trust grade D → A

2026-07-15

Rank Moved

Rank rose 278 spots (#297 → #19)

2026-07-15

HVTrust Changed

HVTrust up 40.2pts (47.3 → 87.5)

2026-07-14

Newly Listed

First tracked at rank #297

GitHub → PyPI: browser-harness

Embed Badge Badge guide for maintainers →

For maintainers

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.2 · Raw JSON