Read 2026-10-23
zenstackhq/zenstack: technical due diligence, read from its repository
What Borehole read in zenstackhq/zenstack's code and history at ee71982: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/orm/src/client/crud-types.ts is 3,162 lines, 45× this codebase's median file
adequateThe median source file here is 70 lines. 11 files exceed 1,000 lines, the largest being 3,162. 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/orm/src/client/crud-types.ts:1 — 3,162 lines (45× median) |
packages/orm/src/client/zod/factory.ts:1 — 2,815 lines (40× median) |
packages/orm/src/client/crud/operations/base.ts:1 — 2,721 lines (38× median) |
packages/server/src/api/rest/index.ts:1 — 2,720 lines (38× median) |
packages/orm/src/client/crud/dialects/base-dialect.ts:1 — 1,979 lines (28× median) |
Engineering Process & SDLC Maturity
strongNo finding.
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/build-test.yml:58 — action pinned by tag |
.github/workflows/build-test.yml:69 — action pinned by tag |
5 shell commands built from strings
adequate5 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
packages/cli/src/actions/init.ts:37 — command run through a shell |
packages/cli/src/actions/proxy.ts:409 — command run through a shell |
packages/cli/src/utils/exec-utils.ts:26 — command run through a shell |
59 locked dependencies have published vulnerabilities, 7 high or critical in what ships
adequate59 of 1,656 locked dependencies match 145 published advisories in OSV, 74 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 — @nuxt/devtools 3.1.1: GHSA-279x-mwfv-vcqv (critical), fixed in 3.3.1; a development dependency |
pnpm-lock.yaml — next 16.1.6: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1; a development dependency |
pnpm-lock.yaml — tar 7.5.9: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; a development dependency |
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 zenstackhq/zenstack: 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.