Read 2026-11-03
d2lang/d2: technical due diligence, read from its repository
What Borehole read in d2lang/d2's code and history at 6a7b483: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
.gitmodules:1: 1 submodule(s) this survey does not read: ci/sub
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate32% of commit subjects are exact repeats of another subject, and subject length varies by only 15.5 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 185× 'changelog' |
| 100× 'update tests' |
| 71× 'next' |
d2renderers/d2svg/d2svg.go is 3,619 lines, 25× this codebase's median file
adequateThe median source file here is 144 lines. 19 files exceed 1,440 lines, the largest being 3,619. 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.
d2renderers/d2svg/d2svg.go:1 — 3,619 lines (25× median) |
d2oracle/edit.go:1 — 3,468 lines (24× median) |
d2ir/d2ir.go:1 — 2,452 lines (17× median) |
d2layouts/d2talalayout/internal/layoutgraph/node.go:1 — 2,444 lines (16× median) |
d2ir/compile.go:1 — 2,410 lines (16× median) |
Engineering Process & SDLC Maturity
adequate28% of commit subjects say nothing about the change
adequate1,155 of 4,082 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 1,155/4,082 low-content subjects (28.3%) |
| 'oss' |
| 'Fix lint' |
| 'cleanup' |
| 'Update test' |
9% of recent commits change more than 2,000 lines
adequate74 of 789 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.
| 74 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
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 5,614 tracked files; 0 present |
The build runs third-party code it does not pin
adequate2 steps pipe a download straight into a shell. 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.
ci/release/_install.sh:17 — download piped into a shell |
1 locked dependency has published vulnerabilities
adequate1 of 38 locked dependencies match 2 published advisories in OSV. 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.
go.mod — golang.org/x/net v0.57.0: GO-2026-6860 (unrated), fixed in 0.62.0 |
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 d2lang/d2: 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.