Read 2026-10-04
caddyserver/caddy: technical due diligence, read from its repository
What Borehole read in caddyserver/caddy's code and history at 69ec5df: 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 | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
.github/CONTRIBUTING.md:171: The project does not take pull requests.github/CONTRIBUTING.md:28: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongcaddyconfig/httpcaddyfile/httptype.go is 1,931 lines, 11× this codebase's median file
adequateThe median source file here is 164 lines. 4 files exceed 1,640 lines, the largest being 1,931. 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.
caddyconfig/httpcaddyfile/httptype.go:1 — 1,931 lines (11× median) |
modules/caddyhttp/reverseproxy/reverseproxy.go:1 — 1,903 lines (11× median) |
modules/caddyhttp/matchers.go:1 — 1,796 lines (10× median) |
modules/caddyhttp/reverseproxy/caddyfile.go:1 — 1,702 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate6 locked dependencies have published vulnerabilities
adequate6 of 169 locked dependencies match 6 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.
go.mod — go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc v0.20.0: GHSA-w34q-cm8f-9c5x (moderate), fixed in 0.21.0 |
go.mod — go.opentelemetry.io/otel/sdk/log v0.20.0: GHSA-hjf4-fphr-2h65 (moderate), fixed in 0.21.0 |
go.mod — go.opentelemetry.io/otel/sdk v1.44.0: GHSA-8wmf-6v46-5gfg (low), fixed in 1.45.0 |
18 advisories against this project in the last 24 months, 9 high or critical
adequateThe newest was published on 2026-07-20. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 8 records name caddy with nothing tying them to this repository (CVE-2017-5963, CVE-2018-19148, CVE-2022-28923, …).
| 2026-07-20: CVE-2026-46415 (high): The Caddy Defender plugin is a middleware for Caddy that allows users to block or manipulate requests based on the client's IP address. Prior to version 0.10.1, |
| 2026-07-10: GHSA-j8px-rmrx-76h9 (moderate), fixed in 2.11.4: Caddy: rewrite placeholder re-expansion, unbounded body buffer DoS, and fileHidden case-sensitivity bypass |
| 2026-07-10: GHSA-6365-7ppr-5r92 (moderate), fixed in v.2.11.5: Connection created for the wrong upstream for forward_auth + reverse_proxy |
| 2026-06-08: GHSA-f59h-q822-g45g (high), fixed in 2.11.4: Caddy: FastCGI header normalization bypass in `forward_auth copy_headers` |
| 2026-06-08: GHSA-qrp7-cvwr-j2c6 (high), fixed in 2.11.4: Caddy: Windows `file_server` path authorization bypass via encoded backslash |
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 caddyserver/caddy: 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.