Is Agent Browser safe?
Agent Browser scores 78.1/100 (Grade B), ranked #52 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
no OSSF Scorecard result yet;
100% of recent commits are signed;
last pushed 2026-07-11. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Strong public trust posture, backed by multiple independent signals.
78.1/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
12.5/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-07-13
Newly Listed
First tracked at rank #52
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-13 10:30 UTC·Repo last pushed 2 days ago
Activity & Reach
Stars
38.4k
Forks
2.5k
Last Push
2026-07-11
2 days ago
Commits (4 wk)
18
Downloads (7d)
923,276
npm
HN mentions (30d)
—
Open Issues
294
Rank Change
NEW
Analysis
HVTrust Dimensions
78.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.5 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
17.0 / 20
AdoptionStars and downloads
19.0 / 20
Activity Inputs
83.9 / 100
StarsRepository reach
27.5 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
15.9 / 25
CommunityFork signal
15.8 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified
Is Agent Browser safe?
Public supply-chain signals for Agent Browser are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Agent Browser carries less obvious unverified-evidence risk than projects with thin signals.
Does Agent Browser publish package provenance?
Yes. Agent Browser's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Agent Browser have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Agent Browser. 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 Agent Browser actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Agent Browser use?
Agent Browser ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Agent Browser's commits signed?
100% of the last 100 commits to Agent Browser 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
medium confidence
Implemented
Agent Browser appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Agent Browser?
HVTrust scores Agent Browser 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) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON
