Is BrowserGym agents safe?
BrowserGym agents scores 49.3/100 (Grade D), ranked #240 of 328 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
no OSSF Scorecard result yet;
recent commits are unsigned;
last pushed 2026-03-17. 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.
49.3/100 · Grade D
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Maintenance
4.3/20
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-06-24
Rank Moved
Rank dropped 28 spots (#195 → #223)
2026-06-23
Rank Moved
Rank dropped 12 spots (#183 → #195)
2026-06-20
Rank Moved
Rank dropped 13 spots (#153 → #166)
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signalsThe repo was last pushed 116 days ago. Fresh activity helps separate stable projects from stale ones.
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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 05:00 UTC·Repo last pushed 116 days ago
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
1.3k
Forks
180
Last Push
2026-03-17
116 days ago
Commits (4 wk)
0
Downloads (7d)
6,923
pypi
HN mentions (30d)
0
Open Issues
18
Rank Change
=
was #240
Analysis
HVTrust Dimensions
49.3 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.5 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
4.3 / 20
AdoptionStars and downloads
12.6 / 20
Activity Inputs
38.1 / 100
StarsRepository reach
18.6 / 30
FreshnessLast push recency
8.9 / 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
—
Unable to query
Is BrowserGym agents safe?
Public trust evidence for BrowserGym agents 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 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 116 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.
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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
browser
code
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 BrowserGym agents'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-06-15
Activity Went Stale
No commits for 90 days
2026-06-05
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-06-05
Mcp Status Changed
Detected MCP server support changed: none → declared
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.
