Read 2026-10-28
vercel/workflow: technical due diligence, read from its repository
What Borehole read in vercel/workflow's code and history at af8c6d3: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
AGENTS.md:469: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongpackages/swc-plugin-workflow/transform/src/lib.rs is 10,502 lines, 128× this codebase's median file
adequateThe median source file here is 82 lines. 42 files exceed 1,000 lines, the largest being 10,502. 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/swc-plugin-workflow/transform/src/lib.rs:1 — 10,502 lines (128× median) |
packages/core/src/runtime.ts:1 — 5,812 lines (70× median) |
packages/core/src/serialization.ts:1 — 4,567 lines (55× median) |
packages/world-local/src/storage/events-storage.ts:1 — 4,111 lines (50× median) |
packages/world-postgres/src/storage.ts:1 — 3,707 lines (45× median) |
Engineering Process & SDLC Maturity
adequateCI runs tests that cannot fail the build
adequate2 test commands in CI end in `|| true` or an equivalent, so the pipeline passes whatever the tests say. A green build then means the tests ran, not that they passed.
.github/workflows/e2e-community-world.yml:228 — a test command that cannot fail |
.github/workflows/e2e-community-world.yml:230 — a test command that cannot fail |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/core/src/serialization-format.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.
packages/core/src/serialization-format.test.ts:302 — test retry |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 shell commands built from strings
adequate2 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/swc-plugin-workflow/build.js:22 — command run through a shell |
workbench/swc-playground/wasm/build.js:16 — command run through a shell |
79 locked dependencies have published vulnerabilities, 57 high or critical in what ships
adequate79 of 3,147 locked dependencies match 184 published advisories in OSV, 83 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.
pnpm-lock.yaml — next 16.3.8: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
pnpm-lock.yaml — piscina 4.9.2: GHSA-67c8-pqhq-4rmx (critical), fixed in 4.9.4 |
pnpm-lock.yaml — tar 7.4.3: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
4 places insert HTML from a variable without sanitising it
adequate4 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
packages/web-shared/src/components/ui/decrypt-button.tsx:33 — HTML from a variable |
packages/web-shared/src/components/ui/load-more-button.tsx:26 — HTML from a variable |
packages/web-shared/src/components/ui/menu-dropdown.tsx:46 — HTML from a variable |
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.
tarballs/vite.config.ts:14 — source maps in a production build |
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 2,270 files for 10 structured logging libraries; 0 matched |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on vercel/workflow: 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.