Read 2026-11-03
getnao/nao: technical due diligence, read from its repository
What Borehole read in getnao/nao's code and history at 04c5075: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:9: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongapps/backend/src/db/sqlite-schema.ts is 2,320 lines, 26× this codebase's median file
adequateThe median source file here is 88 lines. 29 files exceed 1,000 lines, the largest being 2,320. 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/backend/src/db/sqlite-schema.ts:1 — 2,320 lines (26× median) |
apps/backend/src/db/pg-schema.ts:1 — 2,169 lines (24× median) |
apps/backend/src/utils/story-html.tsx:1 — 2,108 lines (23× median) |
apps/frontend/src/components/automations-form.tsx:1 — 2,009 lines (22× median) |
apps/backend/src/services/slack.ts:1 — 1,937 lines (22× median) |
Engineering Process & SDLC Maturity
adequate12% of recent commits change more than 2,000 lines
adequate118 of 1021 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.
| 118 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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate12 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/cli-lint.yml:23 — action pinned by tag |
.github/workflows/cloud-preprod.yml:53 — action pinned by tag |
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
cli/nao_core/config/databases/_clickhouse_native.py:117 — SQL built from a string |
53 locked dependencies have published vulnerabilities, 28 high or critical in what ships
adequate53 of 1,794 locked dependencies match 138 published advisories in OSV, 54 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.
cli/uv.lock — anyio 4.13.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
cli/uv.lock — certifi 2026.2.25: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
package-lock.json — better-auth 1.6.30: GHSA-965c-763c-88jm (critical), fixed in 1.7.7 |
15 places insert HTML from a variable without sanitising it
adequate15 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.
apps/backend/src/components/email/notification-email.tsx:47 — HTML from a variable |
apps/backend/src/mcp/embed/sandbox-html.ts:225 — HTML from a variable |
apps/backend/src/mcp/embed/sandbox-html.ts:262 — HTML from a variable |
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 2,869 files for 10 structured logging libraries; 0 matched |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on getnao/nao: 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.