Is Browser Use Web UI safe?
Browser Use Web UI scores 48.7/100 (Grade D), ranked #242 of 328 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.2/10;
45% of recent commits are signed;
last pushed 2026-05-15. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Thin or incomplete trust evidence. Review carefully before production use.
48.7/100 · Grade D
Strongest Signal
Transparency
12.1/17
Weakest Signal
Safety / Integrity
7.5/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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 refreshed2026-07-11 05:00 UTC·Repo last pushed 57 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
16.2k
Forks
2.7k
Last Push
2026-05-15
57 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
272
Rank Change
=
was #242
Analysis
HVTrust Dimensions
48.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.1 / 17
MaintenanceFreshness and commits
8.2 / 20
AdoptionStars and downloads
10.1 / 20
Activity Inputs
58.5 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
17.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
16.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.2 / 10
OpenSSF Scorecard · scanned Jul 11, 2026
Signed Commits
45%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests1
CII-Best-Practices0
Code-Review9
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained2
Packaging-1
Pinned-Dependencies0
SAST1
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Browser Use Web UI safe?
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.2/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?
Slowing down. Last push was 57 days ago — keep an eye on whether activity resumes.
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.
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.
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.
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.2 · Raw JSON
