Read 2026-11-03
kubernetes/kube-state-metrics: technical due diligence, read from its repository
What Borehole read in kubernetes/kube-state-metrics's code and history at 37caa29: 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 | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:3: names CNCFREADME.md:7: names OpenSSF
Architecture & Codebase — including AI provenance
stronginternal/store/pod.go is 2,062 lines, 12× this codebase's median file
adequateThe median source file here is 161 lines. 1 file exceed 1,610 lines, the largest being 2,062. 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/store/pod.go:1 — 2,062 lines (12× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strong5 locked dependencies have published vulnerabilities, 1 high or critical
adequate5 of 244 locked dependencies match 10 published advisories in OSV, 1 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.
go.mod — github.com/go-jose/go-jose/v4 v4.1.4: GHSA-mgcc-cww5-fp2q (high), fixed in 4.1.6 |
go.mod — github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.6.10: GHSA-xmrv-pmrh-hhx2 (moderate), fixed in 1.7.8 |
go.mod — github.com/aws/aws-sdk-go-v2/service/s3 v1.79.4: GHSA-xmrv-pmrh-hhx2 (moderate), fixed in 1.97.3 |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on kubernetes/kube-state-metrics: 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.