Read 2026-10-23
deepfence/secretscanner: technical due diligence, read from its repository
What Borehole read in deepfence/secretscanner's code and history at 5fa8aee: 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
.gitmodules:1: 1 submodule(s) this survey does not read: agent-plugins-grpc
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate40% of commit subjects are exact repeats of another subject, and subject length varies by only 17.2 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 14× 'Update README.md' |
| 13× 'Update dependencies' |
| 7× 'fix' |
Engineering Process & SDLC Maturity
strongAlmost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 59 tracked files |
Product & Engineering Maturity
strongChange keeps returning to the same few files
adequateFive files out of 96 absorb 35% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
go.mod — 72 commits touched it |
Dockerfile — 55 commits touched it |
README.md — 49 commits touched it |
main.go — 37 commits touched it |
server/http.go — 36 commits touched it |
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.41 to 2.62 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.41, second half 2.62 (split 2023-08-22) |
Go 1.25 is past end of life
adequateThe code is pinned to Go 1.25 (end of life 2026-08-11). None of these receives security fixes any more; the first stopped on 2026-08-11. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
Dockerfile — Go 1.25, end of life 2026-08-11 |
Security & Reliability Posture
adequate1 credential-shaped string in the tree 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.
| Stripe live key, 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 |
3 locked dependencies have published vulnerabilities, 1 high or critical in what ships
adequate3 of 75 locked dependencies match 13 published advisories in OSV, 7 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.
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 deepfence/secretscanner: 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.