Read 2026-11-03
linkerd/linkerd2-proxy: technical due diligence, read from its repository
What Borehole read in linkerd/linkerd2-proxy's code and history at 42decf7: 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 |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:102: states a policy on AI-generated contributionsREADME.md:30: names Cloud Native Computing FoundationREADME.md:31: names CNCF
Architecture & Codebase — including AI provenance
stronglinkerd/app/outbound/src/http/breaker/unified.rs is 1,839 lines, 12× this codebase's median file
adequateThe median source file here is 142 lines. 2 files exceed 1,420 lines, the largest being 1,839. 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.
linkerd/app/outbound/src/http/breaker/unified.rs:1 — 1,839 lines (12× median) |
linkerd/load-biaser/src/lib.rs:1 — 1,586 lines (11× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate14% of bug fixes add or change a test
adequateOf 50 fixes in the last 24 months, 7 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 7 of 50 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, release/19.9.3, is not on the branch this survey read; the newest release on it is linkerd2/v18.9.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag release/19.9.3 |
Security & Reliability Posture
adequate5 credential-shaped strings added in the history sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: private key block, where fakes are usual |
1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
Dockerfile — runs as root |
6 locked dependencies have published vulnerabilities
adequate6 of 465 locked dependencies match 9 published advisories in OSV. 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.
Cargo.lock — rustls 0.23.43: GHSA-2mjx-qc3c-rqvc (moderate), fixed in 0.23.45 |
Cargo.lock — anyhow 1.0.100: RUSTSEC-2026-0190 (unrated), fixed in 1.0.103 |
Cargo.lock — h2 0.4.14: RUSTSEC-2026-0258 (unrated), fixed in 0.4.16 |
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 linkerd/linkerd2-proxy: 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.