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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 20 days ago
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
16.0k
Forks
2.7k
Last Push
2026-05-15
20 days ago
Commits (4 wk)
3
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
319
Rank Change
▼10
was #131
Analysis
HVTrust Dimensions
53.6 / 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
13.1 / 20
AdoptionStars and downloads
10.1 / 20
Activity Inputs
70.9 / 100
StarsRepository reach
25.2 / 30
FreshnessLast push recency
22.2 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
16.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.2 / 10
via deps.dev · OpenSSF
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?
Maintained. Last push was 20 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Browser Use Web UI?
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) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
