Is Stagehand safe to use?

Stagehand has an HVTrust score of 88.9/100 (Grade A), ranked #34 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Stagehand?

Stagehand scores 88.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 25.6k GitHub stars and is categorized under Browser & Computer Use.

Stagehand

Repository

Website by browserbase

The SDK to extract data and interact with any site on the web. Get started with Claude Code, Codex, Eve, Mastra, and more.

Browser & Computer Use TypeScript Listed MIT

Is Stagehand safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 5.0 / 10

Provenance Attested

Signed commits 100%

Last push today

Advisories None known

Compare Stagehand

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

Pick any agent to compare →

Suggest a correction

In detail: Stagehand scores 88.9/100 (Grade A), ranked #34 of 1371 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; OSSF Scorecard rates its supply-chain practices 5.0/10; 100% of recent commits are signed; no published advisory affects its latest release (@browserbasehq/stagehand); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Stagehand could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 5.0 to 9.0lowest checks: CII-Best-Practices 0, Dependency-Update-Tool 0, Fuzzing 0 +5.8 → 94.7 A · #1 of 45

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Stagehand and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/browserbase/stagehand, MIT, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Sep 24, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review10
- Branch Protection5
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies8
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm @browserbasehq/stagehand Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: @browserbasehq/stagehand 4.1.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Stagehand.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions

Verify this score yourself

Every build re-issues Stagehand’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Stagehand compares in Browser & Computer Use

Bars show each HVTrust score; the tick marks Stagehand’s 88.9.

Where the 88.9 comes from

HVTrust dimensions vs the Browser & Computer Use average

88.9 / 100 · 100.0% confidence

Stagehand Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.8 / 25

9.0 above avg 9.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.4 above avg 12.6

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

0.9 above avg 11.9

Maintenance60% last-push freshness · 40% commit activity

19.8 / 20

6.8 above avg 13.0

AdoptionLog-scaled stars · package downloads

18.9 / 20

7.7 above avg 11.2

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.0/10. Tighten the weakest checks to improve public safety evidence.

Compare with OpenClaw Get email alerts for Stagehand View Browser & Computer Use Report missing data

90.9

Activity sub-score · out of 100

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 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 →

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars

25.6k

Forks

1.8k

Last Push

2026-10-09

today

Commits (4 wk)

Downloads (7d)

1,693,657

npm

HN mentions (30d)

Open Issues

103

Rank Change

▼2

was #32

Analysis

Activity Inputs

90.9 / 100

StarsRepository reach

26.4 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

24.4 / 25

CommunityFork signal

15.1 / 20

Common questions about Stagehand

Public supply-chain signals for Stagehand are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Stagehand carries less obvious unverified-evidence risk than projects with thin signals.

Does Stagehand publish package provenance?

Yes. Stagehand's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Stagehand have an OpenSSF Scorecard?

Stagehand has an OpenSSF Scorecard score of 5.0/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 Stagehand actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Stagehand use?

Stagehand ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Stagehand's commits signed?

100% of the last 100 commits to Stagehand 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 Stagehand head-to-head

Stagehand vs OpenClaw → Stagehand vs Browser Harness → Stagehand vs Peekaboo →

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

high confidence

Implemented

Stagehand 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

Extensions

Extension based plugin/integration surface detected.

browser

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 Stagehand'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-09-02

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-08-21

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-08-15

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-10

Provider Removed

Runtime surface shrank — no longer detected: DeepSeek, Google Gemini, Groq, xAI Grok

2026-08-10

Mcp Status Changed

Detected MCP server support changed: declared → none

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependencies: DeepSeek, Google Gemini, Groq, xAI Grok

Maintain Stagehand?

For maintainers

HVTrust scores Stagehand 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

2026-09-03

Grade Changed

Trust grade C → A

2026-09-03

Rank Moved

Rank rose 332 spots (#354 → #22)

2026-09-03

HVTrust Changed

HVTrust up 25.7pts (62.9 → 88.6)

2026-09-02

Mcp Status Changed

Detected MCP server support changed: declared → implemented

2026-09-02

Grade Changed

Trust grade A → C

2026-09-02

Rank Moved

Rank dropped 323 spots (#31 → #354)

2026-09-02

HVTrust Changed

HVTrust down 24.4pts (87.3 → 62.9)

2026-08-31

Grade Changed

Trust grade C → A

2026-08-31

Rank Moved

Rank rose 331 spots (#362 → #31)

2026-08-31

HVTrust Changed

HVTrust up 26.6pts (60.7 → 87.3)

2026-08-30

Grade Changed

Trust grade A → C

2026-08-30

Rank Moved

Rank dropped 332 spots (#30 → #362)

2026-08-30

HVTrust Changed

HVTrust down 26.5pts (87.2 → 60.7)

2026-08-24

Grade Changed

Trust grade C → A

2026-08-24

Rank Moved

Rank rose 282 spots (#311 → #29)

2026-08-24

HVTrust Changed

HVTrust up 26.9pts (60.4 → 87.3)

2026-08-22

Grade Changed

Trust grade A → C

2026-08-22

Rank Moved

Rank dropped 280 spots (#29 → #309)

2026-08-22

HVTrust Changed

HVTrust down 26.5pts (87.0 → 60.5)

2026-08-21

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-08-19

Grade Changed

Trust grade C → A

2026-08-19

Rank Moved

Rank rose 283 spots (#316 → #33)

2026-08-19

HVTrust Changed

HVTrust up 26.4pts (60.3 → 86.7)

2026-08-17

Grade Changed

Trust grade A → C

2026-08-17

Rank Moved

Rank dropped 287 spots (#32 → #319)

2026-08-17

HVTrust Changed

HVTrust down 26.2pts (86.5 → 60.3)

2026-08-15

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-08-13

Grade Changed

Trust grade C → A

2026-08-13

Rank Moved

Rank rose 273 spots (#299 → #26)

2026-08-13

HVTrust Changed

HVTrust up 26.4pts (61.0 → 87.4)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Grade Changed

Trust grade A → C

2026-08-12

Rank Moved

Rank dropped 274 spots (#25 → #299)

2026-08-12

HVTrust Changed

HVTrust down 26.9pts (87.9 → 61.0)

2026-08-10

Provider Removed

Runtime surface shrank — no longer detected: DeepSeek, Google Gemini, Groq, xAI Grok

2026-08-10

Mcp Status Changed

Detected MCP server support changed: declared → none

2026-08-10

Rank Moved

Rank rose 25 spots (#50 → #25)

2026-07-17

Provider Added

Runtime surface grew — new detected provider dependencies: DeepSeek, Google Gemini, Groq, xAI Grok

2026-07-17

Rank Moved

Rank dropped 10 spots (#14 → #24)

GitHub → Website → npm: @browserbasehq/stagehand

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/stagehand.svg)](https://hvtracker.net/agents/stagehand)
            
HTML:
            <a href="https://hvtracker.net/agents/stagehand"><img src="https://hvtracker.net/badge/stagehand.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 · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Stagehand

How Stagehand could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Stagehand compares in Browser & Computer Use

Where the 88.9 comes from

HVTrust dimensions vs the Browser & Computer Use average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Stagehand

Compare Stagehand head-to-head

AI agent surface

Maintain Stagehand?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Browser & Computer Use