updated 2026-08-11 20:32 UTC

Browser Use

browser-use/browser-use

🌐 Make websites accessible for AI agents. Automate tasks online with ease.

Browser & Computer Use Python Grade B Listed MIT
73.8/100
Rank #103 of 1283
Compare Browser Use

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 A · 4/5 signals
Last push
2026-08-11 · 0d ago
Recent change
No recent signal change

Is Browser Use safe? Browser Use scores 73.8/100 (Grade B), ranked #103 of 1283 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 5.0/10; 75% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#5 Skyvern — 81.5 (A) → #6 Argent — 78.6 (B) → #8 Cua — 73.1 (B) → #9 Camofox Browser — 72.0 (B) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/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.
Compare with Browser Harness Get email alerts for Browser Use View Browser & Computer Use Report missing data
99.0
Activity sub-score · out of 100
#7
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-08-11 20:32 UTC · Repo last pushed today

Activity & Reach

Stars
108.8k
Forks
12.0k
Last Push
2026-08-11
today
Commits (4 wk)
163
Downloads (7d)
13,817,744
pypi
HN mentions (30d)
4
Open Issues
97
Rank Change
▼1
was #102

Analysis

HVTrust Dimensions vs Browser & Computer Use

73.8 / 100 · 100.0% confidence

Browser Use Browser & Computer Use average (41 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.0 / 25
2.6 above avg 7.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.6 below avg 12.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
2.0 above avg 10.8
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
6.9 above avg 13.1
AdoptionLog-scaled stars · package downloads
20.0 / 20
8.8 above avg 11.2

Activity Inputs

99.0 / 100
StarsRepository reach
30 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
19.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.0 / 10
OpenSSF Scorecard · scanned Aug 10, 2026
Signed Commits
75%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 7
Contributors 10
Dangerous-Workflow 0
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 2
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is Browser Use safe?

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 5.0/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 1 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?
75% 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.

Compare Browser Use head-to-head

Browser Use vs Browser Harness → Browser Use vs Stagehand → Browser Use vs Agent Browser →

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
6 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
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 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-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 4Grade 1Scorecard 1Score 1HVTrust 1Surface 1
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)
2026-05-29
HVTrust Changed
HVTrust up 9.9pts (56.5 → 66.4)
2026-05-28
Activity Score Changed
Activity score up 25pts (74 → 98)
2026-05-27
Scorecard Added
OSSF Scorecard: 4.6/10
2026-05-27
Grade Changed
Trust grade C → B
2026-05-25
Rank Moved
Rank dropped 12 spots (#9 → #21)
GitHub → PyPI: browser-use

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 73.8 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.3 · Raw JSON