Read 2026-10-04
ocaml/opam: technical due diligence, read from its repository
What Borehole read in ocaml/opam's code and history at 56c6187: 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 | not assessable |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: GPL-3.0 → LGPL-3.0 WITH OCaml-LGPL-linking-exception (2013-05-15) → LGPL-2.1 WITH OCaml-LGPL-linking-exception (2016-06-07)
Architecture & Codebase — including AI provenance
strongsrc/client/opamCommands.ml is 4,667 lines, 45× this codebase's median file
adequateThe median source file here is 102 lines. 20 files exceed 1,020 lines, the largest being 4,667. 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.
src/client/opamCommands.ml:1 — 4,667 lines (45× median) |
src/format/opamFile.ml:1 — 4,391 lines (43× median) |
src/client/opamClient.ml:1 — 2,762 lines (27× median) |
src/solver/opamCudf.ml:1 — 2,077 lines (20× median) |
src/client/opamArg.ml:1 — 1,842 lines (18× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate17 test files against 310 source files (5.5%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 17 test files / 310 source files |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 2.6.0, is not on the branch this survey read; the newest release on it is 2.0.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 2.6.0 |
Security & Reliability Posture
not assessableThe build runs third-party code it does not pin
adequate1 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes 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.
.github/workflows/main.yml:612 — action pinned by tag |
shell/install.sh:594 — download piped into a shell |
Relicensed: GPL-3.0 → LGPL-3.0 WITH OCaml-LGPL-linking-exception (2013-05-15) → LGPL-2.1 WITH OCaml-LGPL-linking-exception (2016-06-07)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-09. 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 1 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 2.0.0. Answer lives in: the release you run, set against each fixed version. CVE-2026-41082 (high) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run.
| 2026-09-09: CVE-2026-57825 (moderate): In the opam package before 2.5.2 for OCaml, the sandbox protection mechanism can be bypassed because symlinks are mishandled during use of .install files. |
| 2026-04-16: CVE-2026-41082 (high): In OCaml opam before 2.5.1, a .install field containing a destination filepath can use ../ to reach a parent directory. |
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/opam: 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.