updated 2026-10-09 08:15 UTC

Browser Use

Repository Website by browser-use

Agents that use the browser.

Browser & Computer Use Python Listed MIT

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

OSSF Scorecard 4.8 / 10
Provenance None
Signed commits 34%
Last push 2d ago
Advisories None known
Compare Browser Use

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

Pick any agent to compare →
Suggest a correction

In detail: Browser Use scores 71.6/100 (Grade B), ranked #310 of 1371 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.8/10; 34% of recent commits are signed; no published advisory affects its latest release (browser-use); last pushed 2026-10-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How Browser Use 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 Use 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-use, MIT, last pushed 2026-10-07. 34% 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.8/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    • PyPI browser-use Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: browser-use 0.13.11. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

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

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Browser Use’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 Use compares in Browser & Computer Use

  1. #10 Cua 77.5 +5.9
  2. #11 Browser4 74.8 +3.2
  3. #12 Browser Use 71.6 this agent
  4. #13 BrowserOS 66.1 −5.5
  5. #14 Obscura 65.3 −6.3

Bars show each HVTrust score; the tick marks Browser Use’s 71.6.

Where the 71.6 comes from

HVTrust dimensions vs the Browser & Computer Use average

71.6 / 100 · 100.0% confidence

Browser Use Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.7 / 25
1.6 below avg 9.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
1.2 above avg 11.4
Maintenance60% last-push freshness · 40% commit activity
19.5 / 20
7.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
20.0 / 20
9.3 above avg 10.7

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-05
Rank Moved
Rank dropped 11 spots (#291 → #302)
2026-09-24
Rank Moved
Rank rose 10 spots (#289 → #279)
2026-09-23
Rank Moved
Rank dropped 180 spots (#109 → #289)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
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 Browser Use View Browser & Computer Use Report missing data
97.8
Activity sub-score · out of 100
#12
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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
117.4k
Forks
13.0k
Last Push
2026-10-07
2 days ago
Commits (4 wk)
80
Downloads (7d)
1,911,897
pypi
HN mentions (30d)
9
Open Issues
168
Rank Change
▼1
was #309

Analysis

Activity Inputs

97.8 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
23.8 / 25
CommunityFork signal
19.1 / 20

Common questions about Browser Use

Browser Use 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 Browser Use publish package provenance?
No published build provenance is currently detected for Browser Use. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Browser Use have an OpenSSF Scorecard?
Browser Use has an OpenSSF Scorecard score of 4.8/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 Use actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Browser Use use?
Browser Use ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Browser Use's commits signed?
34% of the last 100 commits to Browser Use 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
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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 Use'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-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: Browserbase
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Groq

Maintain Browser Use?

For maintainers

HVTrust scores Browser Use 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 14Surface 1Surface 1Surface 1
2026-10-05
Rank Moved
Rank dropped 11 spots (#291 → #302)
2026-09-24
Rank Moved
Rank rose 10 spots (#289 → #279)
2026-09-23
Rank Moved
Rank dropped 180 spots (#109 → #289)
2026-09-21
Rank Moved
Rank rose 173 spots (#282 → #109)
2026-09-13
Rank Moved
Rank dropped 13 spots (#263 → #276)
2026-09-07
Rank Moved
Rank dropped 14 spots (#233 → #247)
2026-09-05
Rank Moved
Rank dropped 53 spots (#176 → #229)
2026-08-31
Rank Moved
Rank dropped 24 spots (#134 → #158)
2026-08-29
Rank Moved
Rank dropped 10 spots (#129 → #139)
2026-08-26
Rank Moved
Rank dropped 15 spots (#103 → #118)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-12
Provider Removed
Runtime surface shrank — no longer detected: Browserbase
2026-08-12
Rank Moved
Rank rose 12 spots (#103 → #91)
2026-08-03
Rank Moved
Rank rose 16 spots (#103 → #87)
2026-07-25
Rank Moved
Rank dropped 11 spots (#89 → #100)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependency: Groq
2026-07-13
Rank Moved
Rank dropped 12 spots (#68 → #80)
GitHub → Website → PyPI: browser-use

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 71.6 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/browser-use.svg)](https://hvtracker.net/agents/browser-use)
HTML:
<a href="https://hvtracker.net/agents/browser-use"><img src="https://hvtracker.net/badge/browser-use.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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON