Read 2026-10-04
vitejs/vite: technical due diligence, read from its repository
What Borehole read in vitejs/vite's code and history at bc598a6: 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 | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
.github/PULL_REQUEST_TEMPLATE.md:16: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongpackages/vite/src/node/plugins/css.ts is 3,686 lines, 409× this codebase's median file
adequateThe median source file here is 9 lines. 13 files exceed 1,000 lines, the largest being 3,686. 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/vite/src/node/plugins/css.ts:1 — 3,686 lines (409× median) |
packages/vite/src/node/config.ts:1 — 2,962 lines (329× median) |
packages/vite/src/node/utils.ts:1 — 2,022 lines (224× median) |
packages/vite/src/node/build.ts:1 — 1,987 lines (220× median) |
packages/vite/src/node/plugins/html.ts:1 — 1,754 lines (194× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strong8 files still carry code deprecated more than two years ago
adequate8 files were marked deprecated over two years ago and still are, the oldest since Jan 2021. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
packages/vite/src/node/optimizer/index.ts — deprecated since Jan 2021 |
packages/vite/src/node/build.ts — deprecated since Jan 2021 |
packages/vite/src/node/config.ts — deprecated since Feb 2021 |
packages/vite/types/importGlob.d.ts — deprecated since Jan 2024 |
packages/vite/src/node/server/hmr.ts — deprecated since Sep 2024 |
Security & Reliability Posture
strong17 locked dependencies have published vulnerabilities, 23 high or critical
adequate17 of 1,304 locked dependencies match 46 published advisories in OSV, 23 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. None of the high or critical ones is in what the product ships: they are development dependencies.
pnpm-lock.yaml — brace-expansion 1.1.15: GHSA-3jxr-9vmj-r5cp (high), fixed in 1.1.16; a development dependency |
pnpm-lock.yaml — brace-expansion 2.1.1: GHSA-3jxr-9vmj-r5cp (high), fixed in 2.1.2; a development dependency |
pnpm-lock.yaml — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10; a development dependency |
17 advisories against this project in the last 24 months, 6 high or critical, 1 on CISA's known-exploited list
adequate1 of them is on CISA's known-exploited list: check first whether the release you run has the fix. The newest was published on 2026-06-01. 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 4 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 8.3.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 20 records name vite with nothing tying them to this repository (CVE-2025-32642, CVE-2025-57753, CVE-2025-59140, …).
| 2025-03-31: GHSA-4r4m-qw57-chr8 (moderate; on CISA's Known Exploited list), fixed in >=4.5.11: `server.fs.deny` bypassed for `inline` and `raw` with `?import` query |
| 2026-06-01: GHSA-fx2h-pf6j-xcff (high), fixed in 0.1.24: `server.fs.deny` bypass on Windows alternate paths |
| 2026-06-01: CVE-2024-52011 (high): launch-editor allows users to open files with line numbers in editor from Node.js. Prior to version 2.9.0, due to the insufficient sanitization of the `file` ar |
| 2026-04-06: GHSA-4w7w-66w2-5vf9 (moderate), fixed in 0.1.16: Path Traversal in Optimized Deps `.map` Handling |
| 2026-04-06: GHSA-v2wj-q39q-566r (high), fixed in 0.1.16: `server.fs.deny` bypassed with queries |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 2,293 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 2,293 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 2,293 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 |
The code branches on the environment's name at 26 places
adequate26 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
packages/vite/src/node/external.ts:51 — branch on the environment name |
packages/vite/src/node/idResolver.ts:67 — branch on the environment name |
packages/vite/src/node/idResolver.ts:67 — branch on the environment name |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on vitejs/vite: 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.