Read 2026-10-04
vapor/vapor: technical due diligence, read from its repository
What Borehole read in vapor/vapor's code and history at 5c5849e: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
AGENTS.md:1: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
not assessableEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.51 to 0.94 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.51, second half 0.94 (split 2021-05-23) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 4.122.2, is not on the branch this survey read; the newest release on it is 4.121.4. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 4.122.2 |
Security & Reliability Posture
adequate1 credential-shaped string committed to the tree
adequateMatches for private key block appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when.
| private key block pattern matched |
Observability & Operations
not assessableNot rated: only 4 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 vapor/vapor: 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.