Read 2026-10-04
ocaml-ppx/ocamlformat: technical due diligence, read from its repository
What Borehole read in ocaml-ppx/ocamlformat's code and history at 56cf9d5: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
stronglib/Fmt_ast.ml is 5,213 lines, 124× this codebase's median file
adequateThe median source file here is 42 lines. 4 files exceed 1,000 lines, the largest being 5,213. 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.
lib/Fmt_ast.ml:1 — 5,213 lines (124× median) |
lib/Ast.ml:1 — 2,559 lines (60× median) |
lib/Conf.ml:1 — 1,628 lines (38× median) |
lib/Params.ml:1 — 1,254 lines (29× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
not assessableEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.65 to 0.84 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.65, second half 0.84 (split 2022-03-30) |
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 3,456 tracked files; 0 present |
The build runs third-party code it does not pin
adequate5 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/build-dune.yml:17 — action pinned by tag |
.github/workflows/build-linux.yml:32 — action pinned by tag |
2 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.
vendor/ocamlformat-stdlib — 9 tracked files, no licence file |
vendor/odoc-parser — 15 tracked files, no licence file |
Observability & Operations
not assessableNot rated: only 4 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 ocaml-ppx/ocamlformat: 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.