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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed 3 days ago
Rank Trend
2026-05-232026-06-04
Activity & Reach
Stars
97.1k
Forks
10.9k
Last Push
2026-06-01
3 days ago
Commits (4 wk)
98
Downloads (7d)
8,830,231
pypi
HN mentions (30d)
5
Open Issues
258
Rank Change
▼2
was #57
Analysis
HVTrust Dimensions
71.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
8.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.4 / 17
MaintenanceFreshness and commits
19.8 / 20
AdoptionStars and downloads
20.0 / 20
Activity Inputs
98.3 / 100
StarsRepository reach
29.9 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
24.9 / 25
CommunityFork signal
18.8 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
via deps.dev · OpenSSF
Signed Commits
49%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests10
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST6
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities10
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 4.6/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 3 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?
49% 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.
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?
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.
