Read 2026-10-23
prisma/orm: technical due diligence, read from its repository
What Borehole read in prisma/orm's code and history at f543fb4: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:120: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongpackages/3-extensions/sql-orm-client/src/collection.ts is 3,102 lines, 38× this codebase's median file
adequateThe median source file here is 81 lines. 42 files exceed 1,000 lines, the largest being 3,102. 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/3-extensions/sql-orm-client/src/collection.ts:1 — 3,102 lines (38× median) |
packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:1 — 2,855 lines (35× median) |
packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts:1 — 2,789 lines (34× median) |
packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts:1 — 2,741 lines (33× median) |
packages/3-extensions/sql-orm-client/src/types.ts:1 — 2,440 lines (30× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/3-targets/sqlite/2-adapter/test/migrations/create-table-call-lowering.test.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.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 7.10.1, is not on the branch this survey read; the newest release on it is v0.17.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 7.10.1 |
Security & Reliability Posture
adequate9 SQL statements built from strings
adequate9 places in product code build SQL by formatting or joining strings rather than passing parameters. 2 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
packages/3-targets/mysql/1-target/src/core/marker-lock.ts:22 — SQL built from a string |
packages/3-targets/mysql/1-target/src/core/marker-lock.ts:40 — SQL built from a string |
packages/3-targets/postgres/3-driver/src/session-settings.ts:111 — SQL built from a string |
33 locked dependencies have published vulnerabilities, 21 high or critical in what ships
adequate33 of 1,106 locked dependencies match 157 published advisories in OSV, 49 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 — dompurify 3.4.8: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
pnpm-lock.yaml — next 16.3.0: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
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 10,130 files for 10 structured logging libraries; 0 matched |
The service logs with print: 104 calls against 14 logger calls
adequate104 `print` or `console.log` calls in the service's code, and 14 calls through a logger. Printed lines carry no level and no context, cannot be switched off, and are hard to find again in production.
apps/lsp-playground/src/bridge.ts:83 — print used for logging |
apps/lsp-playground/src/cli.ts:61 — print used for logging |
apps/lsp-playground/src/cli.ts:62 — print used for logging |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on prisma/orm: 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.