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 79 days ago
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
1.2k
Forks
176
Last Push
2026-03-17
79 days ago
Commits (4 wk)
0
Downloads (7d)
8,880
pypi
HN mentions (30d)
0
Open Issues
33
Rank Change
▼12
was #119
Analysis
HVTrust Dimensions
58.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.2 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
6.7 / 20
AdoptionStars and downloads
12.7 / 20
Activity Inputs
43.3 / 100
StarsRepository reach
18.6 / 30
FreshnessLast push recency
14.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.5 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
94%
of last 100 commits verified
Is BrowserGym agents safe?
BrowserGym agents 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 BrowserGym agents publish package provenance?
Yes. BrowserGym agents's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does BrowserGym agents have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for BrowserGym agents. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is BrowserGym agents actively maintained?
Slowing down. Last push was 79 days ago — keep an eye on whether activity resumes.
What license does BrowserGym agents use?
BrowserGym agents ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BrowserGym agents's commits signed?
94% of the last 100 commits to BrowserGym agents 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 BrowserGym agents?
HVTrust scores BrowserGym agents 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.
