Read 2026-10-23
browser-use/browser-harness: technical due diligence, read from its repository
What Borehole read in browser-use/browser-harness's code and history at ea0d03e: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongsrc/browser_harness/admin.py is 1,589 lines, 12× this codebase's median file
adequateThe median source file here is 129 lines. 1 file exceed 1,290 lines, the largest being 1,589. 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.
src/browser_harness/admin.py:1 — 1,589 lines (12× median) |
35 errors caught and discarded in product code
adequate35 places catch an error and do nothing with it, across 8 files (0.7 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
src/browser_harness/admin.py:310 — error caught and discarded |
src/browser_harness/admin.py:314 — error caught and discarded |
src/browser_harness/admin.py:538 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
not assessableNot rated: only 9 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 244 tracked files; 0 present |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on browser-use/browser-harness: 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.