updated 2026-10-09 16:07 UTC

Browser Use Web UI

Repository by browser-use

🖥️ Run AI Agent in your browser.

Browser & Computer Use Python Listed MIT

Is Browser Use Web UI safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.0 / 10
Provenance None
Signed commits 45%
Last push 14d ago
Compare Browser Use Web UI

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

Pick any agent to compare →
Suggest a correction

In detail: Browser Use Web UI scores 51.2/100 (Grade C), ranked #935 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.0/10; 45% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Browser Use Web UI 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 Web UI and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/browser-use/web-ui, MIT, last pushed 2026-09-25. 45% 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.0/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. Browser Use Web UI is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

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

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

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

  1. #27 autoMate 51.4 +0.2
  2. #28 Magentic-UI 51.3 +0.1
  3. #29 Browser Use Web UI 51.2 this agent
  4. #30 Nanobrowser 50.4 −0.8
  5. #31 OpenAI CUA Sample App 49.3 −1.9

Bars show each HVTrust score; the tick marks Browser Use Web UI’s 51.2.

Where the 51.2 comes from

HVTrust dimensions vs the Browser & Computer Use average

51.2 / 100 · 100.0% confidence

Browser Use Web UI Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.3 / 25
2.5 below avg 9.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
11.9 / 17
in line with avg 11.9
Maintenance60% last-push freshness · 40% commit activity
11.1 / 20
1.9 below avg 13.0
AdoptionLog-scaled stars · package downloads
10.1 / 20
1.1 below avg 11.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-30
Rank Moved
Rank dropped 10 spots (#883 → #893)
2026-09-25
Activity Resumed
Activity resumed
2026-09-25
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.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.
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 Web UI View Browser & Computer Use Report missing data
64.4
Activity sub-score · out of 100
#29
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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-09 16:07 UTC · Repo last pushed 14 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
16.6k
Forks
2.8k
Last Push
2026-09-25
14 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
271
Rank Change
▼9
was #926

Analysis

Activity Inputs

64.4 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.0 / 20

Common questions about Browser Use Web UI

Public trust evidence for Browser Use Web UI is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Browser Use Web UI publish package provenance?
No published build provenance is currently detected for Browser Use Web UI. 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 Web UI have an OpenSSF Scorecard?
Browser Use Web UI has an OpenSSF Scorecard score of 4.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 Web UI actively maintained?
Maintained. Last push was 14 days ago.
What license does Browser Use Web UI use?
Browser Use Web UI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Browser Use Web UI's commits signed?
45% of the last 100 commits to Browser Use Web UI 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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
N/A
No package source configured
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 Web UI'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-25
Activity Resumed
Activity resumed
2026-08-13
Activity Went Stale
No commits for 90 days

Maintain Browser Use Web UI?

For maintainers

HVTrust scores Browser Use Web UI 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 30Stale 1Score 1HVTrust 1Grade 1Fresh 1
2026-09-30
Rank Moved
Rank dropped 10 spots (#883 → #893)
2026-09-25
Activity Resumed
Activity resumed
2026-09-25
Grade Changed
Trust grade D → C
2026-09-25
Rank Moved
Rank rose 213 spots (#1094 → #881)
2026-09-25
HVTrust Changed
HVTrust up 8.8pts (43.3 → 52.1)
2026-09-25
Activity Score Changed
Activity score up 18pts (48 → 66)
2026-09-23
Rank Moved
Rank dropped 624 spots (#467 → #1091)
2026-09-22
Rank Moved
Rank dropped 96 spots (#371 → #467)
2026-09-21
Rank Moved
Rank rose 714 spots (#1085 → #371)
2026-09-12
Rank Moved
Rank dropped 13 spots (#1063 → #1076)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1040 → #1056)
2026-09-07
Rank Moved
Rank dropped 36 spots (#995 → #1031)
2026-09-06
Rank Moved
Rank dropped 15 spots (#980 → #995)
2026-09-05
Rank Moved
Rank dropped 48 spots (#932 → #980)
2026-09-04
Rank Moved
Rank dropped 30 spots (#902 → #932)
2026-09-03
Rank Moved
Rank dropped 53 spots (#849 → #902)
2026-09-02
Rank Moved
Rank dropped 43 spots (#806 → #849)
2026-09-01
Rank Moved
Rank dropped 31 spots (#775 → #806)
2026-08-31
Rank Moved
Rank dropped 37 spots (#738 → #775)
2026-08-30
Rank Moved
Rank dropped 25 spots (#713 → #738)
2026-08-29
Rank Moved
Rank dropped 50 spots (#663 → #713)
2026-08-28
Rank Moved
Rank dropped 22 spots (#641 → #663)
2026-08-27
Rank Moved
Rank dropped 17 spots (#624 → #641)
2026-08-26
Rank Moved
Rank dropped 96 spots (#528 → #624)
2026-08-24
Rank Moved
Rank dropped 13 spots (#514 → #527)
2026-08-22
Rank Moved
Rank rose 10 spots (#526 → #516)
2026-08-19
Rank Moved
Rank dropped 10 spots (#515 → #525)
2026-08-13
Activity Went Stale
No commits for 90 days
2026-08-13
Rank Moved
Rank dropped 14 spots (#496 → #510)
2026-08-10
Rank Moved
Rank dropped 19 spots (#484 → #503)
2026-08-08
Rank Moved
Rank dropped 127 spots (#353 → #480)
2026-07-29
Rank Moved
Rank dropped 11 spots (#322 → #333)
2026-07-15
Rank Moved
Rank dropped 23 spots (#290 → #313)
2026-07-14
Rank Moved
Rank dropped 13 spots (#277 → #290)
2026-07-13
Rank Moved
Rank dropped 33 spots (#244 → #277)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 51.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/browser-use-web-ui.svg)](https://hvtracker.net/agents/browser-use-web-ui)
HTML:
<a href="https://hvtracker.net/agents/browser-use-web-ui"><img src="https://hvtracker.net/badge/browser-use-web-ui.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

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