Read 2026-10-23
browserbase/stagehand: technical due diligence, read from its repository
What Borehole read in browserbase/stagehand's code and history at 0f93c29: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/integrations/core/src/facade/runtime.ts is 3,626 lines, 35× this codebase's median file
adequateThe median source file here is 101 lines. 14 files exceed 1,010 lines, the largest being 3,626. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
packages/integrations/core/src/facade/runtime.ts:1 — 3,626 lines (35× median) |
packages/extension/understudy/page.ts:1 — 2,785 lines (27× median) |
packages/sdk-python/src/stagehand/_generated/models.py:1 — 2,597 lines (25× median) |
packages/protocol/schemas.ts:1 — 2,180 lines (21× median) |
packages/evals/lib/braintrust-report.ts:1 — 1,512 lines (14× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
packages/cli/Dockerfile — runs as root |
23 locked dependencies have published vulnerabilities, 11 high or critical in what ships
adequate23 of 2,012 locked dependencies match 38 published advisories in OSV, 23 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
packages/integrations/crewai/uv.lock — chromadb 1.5.9: GHSA-36p7-vc44-83pf (critical) |
pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
pnpm-lock.yaml — tinypool 2.1.0: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2025-11-25. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 2.2.0. Answer lives in: the release you run, set against each fixed version.
| 2025-11-25: MAL-2025-191198 (unrated): Malicious code in @browserbasehq/stagehand (npm) |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on browserbase/stagehand: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.