Read 2026-10-23
emdash-cms/emdash: technical due diligence, read from its repository
What Borehole read in emdash-cms/emdash's code and history at 0eefcfe: 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
.github/PULL_REQUEST_TEMPLATE.md:22: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongapps/labeler/worker-configuration.d.ts is 15,111 lines, 118× this codebase's median file
adequateThe median source file here is 128 lines. 61 files exceed 1,280 lines, the largest being 15,111. 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/labeler/worker-configuration.d.ts:1 — 15,111 lines (118× median) |
apps/release-service/worker-configuration.d.ts:1 — 15,106 lines (118× median) |
apps/aggregator/worker-configuration.d.ts:1 — 15,097 lines (117× median) |
infra/flue-review/worker-configuration.d.ts:1 — 15,090 lines (117× median) |
apps/release-verifier/worker-configuration.d.ts:1 — 15,076 lines (117× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e/playground/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
e2e/playground/playwright.config.ts:11 — test retry |
7% of recent commits change more than 2,000 lines
adequate126 of 1719 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.
| 126 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 |
2 SQL statements built from strings
adequate2 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.
packages/cloudflare/src/db/do-sql-class.ts:232 — SQL built from a string |
packages/core/src/search/fts-manager.ts:377 — SQL built from a string |
61 locked dependencies have published vulnerabilities, 45 high or critical in what ships
adequate61 of 1,882 locked dependencies match 170 published advisories in OSV, 66 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.
pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
pnpm-lock.yaml — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
pnpm-lock.yaml — tinypool 2.1.0: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
14 places insert HTML from a variable without sanitising it
adequate14 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.
infra/perf-monitor/public/index.html:934 — HTML from a variable |
packages/admin/src/components/MarketplacePluginDetail.tsx:282 — HTML from a variable |
packages/admin/src/components/RegistryPluginDetail.tsx:871 — 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 4,654 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 emdash-cms/emdash: 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.