updated 2026-08-09 19:01 UTC

Agent Browser

vercel-labs/agent-browser

Browser automation CLI for AI agents

Browser & Computer Use Rust Grade A Listed Apache-2.0
86.9/100
Rank #26 of 1204
Compare Agent Browser

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-08 · 1d ago
Recent change
Tool Surface Changed

Is Agent Browser safe? Agent Browser scores 86.9/100 (Grade A), ranked #26 of 1204 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; OSSF Scorecard rates its supply-chain practices 4.3/10; 100% of recent commits are signed; last pushed 2026-08-08. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#1 Browser Harness — 88.1 (A) → #3 OpenClaw — 86.5 (A) → #4 Stagehand — 84.7 (A) → #5 Skyvern — 81.5 (A) →

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-07-14
Scorecard Added
OSSF Scorecard: 3.8/10
2026-07-14
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.
Compare with Browser Harness Get email alerts for Agent Browser View Browser & Computer Use Report missing data
87.1
Activity sub-score · out of 100
#2
In Browser & Computer Use

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 refreshed 2026-08-09 19:01 UTC · Repo last pushed yesterday

Activity & Reach

Stars
40.3k
Forks
2.6k
Last Push
2026-08-08
yesterday
Commits (4 wk)
30
Downloads (7d)
923,276
npm
HN mentions (30d)
—
Open Issues
327
Rank Change
▲1
was #27

Analysis

HVTrust Dimensions vs Browser & Computer Use

86.9 / 100 · 100.0% confidence

Agent Browser Browser & Computer Use average (34 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
17.9 / 25
10.1 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
5.9 above avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
1.0 above avg 11.2
Maintenance60% last-push freshness · 40% commit activity
17.9 / 20
5.9 above avg 12.0
AdoptionLog-scaled stars · package downloads
19.0 / 20
8.2 above avg 10.8

Activity Inputs

87.1 / 100
StarsRepository reach
27.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
18.6 / 25
CommunityFork signal
15.9 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
4.3 / 10
OpenSSF Scorecard · scanned Aug 9, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 9
CII-Best-Practices 0
Code-Review 5
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

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?
Agent Browser has an OpenSSF Scorecard score of 4.3/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 Agent Browser actively maintained?
Actively maintained. The repository was pushed to within the last 1 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.

Compare Agent Browser head-to-head

Agent Browser vs Browser Harness → Agent Browser vs OpenClaw → Agent Browser vs Stagehand →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared 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
How this surface has changed

Detected changes to Agent Browser'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-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared

Maintain Agent Browser?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1HVTrust 1Rank 1Grade 1Scorecard 1Surface 1
2026-08-07
Tool Surface Changed
Detected tool/plugin surface changed: extension-based → declared
2026-07-14
Scorecard Added
OSSF Scorecard: 3.8/10
2026-07-14
Grade Changed
Trust grade B → A
2026-07-14
Rank Moved
Rank rose 19 spots (#51 → #32)
2026-07-14
HVTrust Changed
HVTrust up 7.0pts (78.4 → 85.4)
2026-07-13
Newly Listed
First tracked at rank #51
GitHub → npm: agent-browser

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 86.9 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/agent-browser.svg)](https://hvtracker.net/agents/agent-browser)
HTML:
<a href="https://hvtracker.net/agents/agent-browser"><img src="https://hvtracker.net/badge/agent-browser.svg" alt="HVTrust"></a>

Other agents in Browser & Computer Use

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON