Read 2026-10-04
nestjs/nest: technical due diligence, read from its repository
What Borehole read in nestjs/nest's code and history at 9feedff: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/core/injector/injector.ts is 1,359 lines, 52× this codebase's median file
adequateThe median source file here is 26 lines. 4 files exceed 1,000 lines, the largest being 1,359. 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/core/injector/injector.ts:1 — 1,359 lines (52× median) |
packages/microservices/external/kafka.interface.ts:1 — 1,326 lines (51× median) |
packages/platform-fastify/adapters/fastify-adapter.ts:1 — 1,209 lines (46× median) |
packages/common/decorators/http/route-params.decorator.ts:1 — 1,133 lines (43× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/testing/test/capturing-logger.service.spec.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.
packages/testing/test/capturing-logger.service.spec.ts:33 — test retry |
Product & Engineering Maturity
adequateFixes are 50% of recent work, up from 30%
adequateIn the last two quarters 50% of commits were fixes, against 30% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 62%, 39%, 30%, 30%, 38%, 34%, 24%, 25% |
Security & Reliability Posture
adequate6 locked dependencies have published vulnerabilities, 3 high or critical in what ships
adequate6 of 172 locked dependencies match 9 published advisories in OSV, 3 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.
package-lock.json — engine.io 6.6.9: GHSA-2gc4-cqfq-p2gv (high), fixed in 6.6.10 |
package-lock.json — socket.io-parser 4.2.6: GHSA-2m8v-j782-fhvr (high), fixed in 4.2.7 |
package-lock.json — ws 8.18.3: GHSA-96hv-2xvq-fx4p (high), fixed in 8.21.0 |
11 advisories against this project in the last 24 months, 8 high or critical
adequateThe newest was published on 2026-09-15. 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 2 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 12.1.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 18 records name nest with nothing tying them to this repository (CVE-2019-5034, CVE-2019-5035, CVE-2019-5036, …).
| 2026-09-15: GHSA-m8vh-jmq9-5rjg (high), fixed in 12.0.2 and 11.2.4: Remote process termination via a deeply nested microservice message pattern |
| 2026-09-15: GHSA-9c5c-9qcx-q35q (high), fixed in 12.0.2 and 11.2.4: Path-scoped middleware bypass via absolute-form request targets |
| 2026-09-15: GHSA-96h4-vgxj-gvm2 (moderate), fixed in 11.2.5: Unbounded memory growth in the NestJS TCP microservice transport |
| 2026-06-08: GHSA-6v32-fjc9-9qf6 (high), fixed in 11.1.24: Middleware Bypass on Fastify via Trailing Slash |
| 2026-04-13: GHSA-hpwf-8g29-85qm (high), fixed in 11.1.19: DoS via Recursive handleData in JsonSocket (TCP Transport) |
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 nestjs/nest: 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.