Read 2026-10-23
rowboatlabs/rowboat: technical due diligence, read from its repository
What Borehole read in rowboatlabs/rowboat's code and history at 31931b3: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongapps/x/apps/renderer/src/App.tsx is 8,293 lines, 72× this codebase's median file
adequateThe median source file here is 114 lines. 33 files exceed 1,140 lines, the largest being 8,293. 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.
apps/x/apps/renderer/src/App.tsx:1 — 8,293 lines (72× median) |
apps/x/packages/shared/src/ipc.ts:1 — 4,646 lines (40× median) |
apps/x/apps/renderer/src/components/email-view.tsx:1 — 4,041 lines (35× median) |
apps/x/apps/main/src/ipc.ts:1 — 3,272 lines (28× median) |
apps/x/packages/core/src/runtime/assembly/skills/pdf-slides/skill.ts:1 — 2,754 lines (24× median) |
Engineering Process & SDLC Maturity
strongAlmost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 1,739 tracked files |
Product & Engineering Maturity
adequate17% of bug fixes add or change a test
adequateOf 504 fixes in the last 24 months, 87 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 87 of 504 |
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 1,739 tracked files; 0 present |
1 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.
apps/harbor/Dockerfile — runs as root |
2 SQL statements built from strings
adequate2 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
apps/harbor/packages/server/src/connectors/posthog/index.ts:111 — SQL built from a string |
apps/harbor/packages/server/src/connectors/posthog/index.ts:125 — SQL built from a string |
2 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
apps/x/apps/main/bundle.mjs:150 — command run through a shell |
apps/x/packages/core/src/code-mode/acp/shell-env.ts:25 — command run through a shell |
67 locked dependencies have published vulnerabilities, 58 high or critical in what ships
adequate67 of 2,582 locked dependencies match 161 published advisories in OSV, 84 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.
apps/x/pnpm-lock.yaml — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; a development dependency |
apps/harbor/pnpm-lock.yaml — tinypool 1.1.1: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
apps/x/pnpm-lock.yaml — @isaacs/brace-expansion 5.0.0: GHSA-7h2j-956f-4vf2 (high), fixed in 5.0.1 |
3 advisories against this project in the last 24 months
adequateThe newest was published on 2026-09-05. 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 3 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 1.0.5. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names rowboat with nothing tying it to this repository (CVE-2026-6635).
| 2026-09-05: CVE-2026-86122 (moderate): Rowboat through 0.9.1 fails to validate custom MCP server and webhook URLs, allowing authenticated users to configure arbitrary destinations. Attackers can poin |
| 2026-09-02: CVE-2026-84856 (moderate): A vulnerability was detected in rowboatlabs rowboat up to 0.9.1. The impacted element is the function request.text/req.json of the file apps/rowboat/app/api/com |
| 2025-07-07: CVE-2025-7115 (moderate): A vulnerability was found in rowboatlabs rowboat up to 8096eaf63b5a0732edd8f812bee05b78e214ee97. It has been rated as critical. Affected by this issue is the fu |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 1,617 files for 10 structured logging libraries; 0 matched |
No 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 rowboatlabs/rowboat: 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.