Read 2026-10-23
clientio/joint: technical due diligence, read from its repository
What Borehole read in clientio/joint's code and history at f25f357: 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 |
Architecture & Codebase — including AI provenance
strongpackages/joint-core/src/dia/Paper.mjs is 4,347 lines, 47× this codebase's median file
adequateThe median source file here is 91 lines. 12 files exceed 1,000 lines, the largest being 4,347. 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.
packages/joint-core/src/dia/Paper.mjs:1 — 4,347 lines (47× median) |
packages/joint-core/types/dia.d.ts:1 — 2,758 lines (30× median) |
packages/joint-core/src/V/index.mjs:1 — 2,577 lines (28× median) |
packages/joint-core/src/util/utilHelpers.mjs:1 — 2,475 lines (27× median) |
packages/joint-core/src/g/path.mjs:1 — 2,261 lines (24× median) |
Engineering Process & SDLC Maturity
adequate6% of recent commits change more than 2,000 lines
adequate14 of 221 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.
| 14 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate6 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/release.yml:86 — action pinned by tag |
.github/workflows/release.yml:128 — action pinned by tag |
64 locked dependencies have published vulnerabilities, 87 high or critical
adequate64 of 2,692 locked dependencies match 163 published advisories in OSV, 87 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
packages/joint-layout-directed-graph/rollup.config.mjs:75 — source maps in a production build |
packages/joint-layout-elk/rollup.config.mjs:107 — source maps in a production build |
packages/joint-layout-msagl/rollup.config.mjs:76 — source maps in a production build |
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 clientio/joint: 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.