Read 2026-11-03
adguardteam/adguardhome: technical due diligence, read from its repository
What Borehole read in adguardteam/adguardhome's code and history at 3e0cb52: 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
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:45: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
stronginternal/filtering/servicelist.go is 3,444 lines, 49× this codebase's median file
adequateThe median source file here is 70 lines. 8 files exceed 1,000 lines, the largest being 3,444. 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.
internal/filtering/servicelist.go:1 — 3,444 lines (49× median) |
client_v2/src/api/generated.ts:1 — 1,514 lines (21× median) |
internal/home/home.go:1 — 1,503 lines (21× median) |
internal/dhcpd/v4_unix.go:1 — 1,454 lines (20× median) |
internal/filtering/filtering.go:1 — 1,210 lines (17× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (client/playwright.config.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.
client/playwright.config.ts:19 — test retry |
Product & Engineering Maturity
strong9 files still carry code deprecated more than two years ago
adequate9 files were marked deprecated over two years ago and still are, the oldest since Mar 2023. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
internal/home/clientshttp.go — deprecated since Mar 2023 |
internal/querylog/http.go — deprecated since Mar 2023 |
internal/stats/http.go — deprecated since Mar 2023 |
internal/filtering/safesearchhttp.go — deprecated since Mar 2023 |
internal/home/options.go — deprecated since Apr 2023 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.107.80, is not on the branch this survey read; the newest release on it is v0.107.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.107.80 |
Security & Reliability Posture
adequate8 locked dependencies have published vulnerabilities, 10 high or critical in what ships
adequate8 of 446 locked dependencies match 22 published advisories in OSV, 16 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.
client_v2/package-lock.json — seroval 1.5.4: GHSA-p6vx-979v-rg4c (critical), fixed in 1.6.2 |
client/package-lock.json — decode-uri-component 0.2.2: GHSA-qr28-fpjm-wq7f (high), fixed in 0.5.1 |
client/package-lock.json — nanoid 3.3.8: GHSA-28wg-ghj8-5hjv (high), fixed in 3.3.16 |
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.
client/src/components/Filters/Services/ServiceField.tsx:34 — HTML from a variable |
client/src/components/Settings/Clients/ClientsTable/ClientsTable.tsx:245 — HTML from a variable |
client/src/components/ui/Card.tsx:22 — 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.
client/webpack.dev.js:51 — source maps in a production build |
client_v2/webpack.dev.js:48 — source maps in a production build |
3 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-07-13. 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 3 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 0.107.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names adguardhome with nothing tying it to this repository (CVE-2024-36586).
| 2026-07-13: GHSA-73vv-3434-p64c (low), fixed in v0.107.76: AdGuard Home DoQ Shared-Budget Starvation Enables Remote Unauthenticated DoS |
| 2026-05-19: GHSA-xgx4-4h9w-53pv (moderate), fixed in 0.107.75: AdGuard Home: DoQ-to-UDP State Reduction and Source-Port Oracle |
| 2026-03-11: GHSA-5fg6-wrq4-w5gh (critical), fixed in 0.107.73: AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass |
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 adguardteam/adguardhome: 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.