Read 2026-11-03
browseros-ai/browseros: technical due diligence, read from its repository
What Borehole read in browseros-ai/browseros's code and history at 157eadd: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
.gitmodules:1: 1 submodule(s) this survey does not read: .internal-docs
Architecture & Codebase — including AI provenance
strongpackages/browseros-agent/apps/claw-server/src/api/mcp/service.rs is 3,908 lines, 42× this codebase's median file
adequateThe median source file here is 93 lines. 51 files exceed 1,000 lines, the largest being 3,908. 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/browseros-agent/apps/claw-server/src/api/mcp/service.rs:1 — 3,908 lines (42× median) |
packages/browseros-agent/apps/claw-server/src/api/mcp/effects/tab_groups.rs:1 — 3,497 lines (37× median) |
packages/browseros-agent/crates/browseros-core/src/target/tests.rs:1 — 3,416 lines (36× median) |
packages/browseros-agent/crates/browseros-mcp/src/tests.rs:1 — 3,080 lines (33× median) |
packages/browseros-agent/apps/claw-server/src/db/migration.rs:1 — 2,566 lines (27× median) |
Engineering Process & SDLC Maturity
adequate7% of recent commits change more than 2,000 lines
adequate205 of 2981 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 205 commits over 2,000 lines |
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/browseros/docker/neo/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate13 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/audit.yml:21 — action pinned by tag |
.github/workflows/bos-build-tests.yml:51 — action pinned by tag |
10 locked dependencies have published vulnerabilities, 29 high or critical in what ships
adequate10 of 453 locked dependencies match 58 published advisories in OSV, 29 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
packages/browseros/uv.lock — certifi 2025.10.5: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
packages/browseros/uv.lock — pillow 12.3.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0 |
packages/browseros-agent/Cargo.lock — rustls 0.23.41: GHSA-2mjx-qc3c-rqvc (moderate), fixed in 0.23.45 |
5 places insert HTML from a variable without sanitising it
adequate5 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
packages/browseros-agent/apps/app/components/ai-elements/code-block.tsx:116 — HTML from a variable |
packages/browseros-agent/apps/app/components/ai-elements/code-block.tsx:121 — HTML from a variable |
packages/browseros-agent/apps/claw-app/components/ai-elements/schema-display.tsx:110 — HTML from a variable |
3 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
packages/browseros/chromium_patches/third_party/libxml — 1 tracked files, no licence file |
packages/browseros/chromium_patches/third_party/sparkle — 1 tracked files, no licence file |
packages/browseros/chromium_patches/third_party/winsparkle — 2 tracked files, no licence file |
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on browseros-ai/browseros: 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.