Read 2026-10-22
k3s-io/k3s: technical due diligence, read from its repository
What Borehole read in k3s-io/k3s's code and history at 65d7127: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:23: states a policy on AI-generated contributionsGOVERNANCE.md:9: names CNCFREADME.md:8: names OpenSSFREADME.md:116: names Linux Foundation
Architecture & Codebase — including AI provenance
strongpkg/etcd/etcd.go is 1,696 lines, 18× this codebase's median file
adequateThe median source file here is 94 lines. 3 files exceed 1,000 lines, the largest being 1,696. 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.
pkg/etcd/etcd.go:1 — 1,696 lines (18× median) |
install.sh:1 — 1,219 lines (12× median) |
pkg/etcd/snapshot.go:1 — 1,007 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate100 direct dependencies in a single manifest
adequatego.mod declares 100 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 100 declared |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.0.1, is not on the branch this survey read; the newest release on it is v1.0.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.0.1 |
Security & Reliability Posture
adequate2 Dockerfiles run 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 |
package/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 steps pipe a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
install.sh:77 — download piped into a shell |
2 of 3 Kubernetes workloads declare no resource limits
adequate2 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
manifests/local-storage.yaml — workload with no limits |
manifests/metrics-server/metrics-server-deployment.yaml — workload with no limits |
7 locked dependencies have published vulnerabilities, 6 high or critical in what ships
adequate7 of 465 locked dependencies match 19 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.
go.mod — github.com/cloudnativelabs/kube-router/v2 v2.0.0-00010101000000-000000000000: GHSA-phqm-jgc3-qf8g (high); pinned to a commit or a branch, so whether it has the fix needs the dependency's own source |
go.mod — github.com/containerd/containerd/v2 v2.2.3: GHSA-33vj-92qq-66hc (high), fixed in 2.2.5 |
go.mod — github.com/docker/docker v28.5.2+incompatible: GO-2026-4887 (high) |
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
pkg/daemons/control/deps/deps.go — 1 tracked files, no licence file |
2 advisories against this project in the last 24 months
adequateThe newest was published on 2026-06-03. 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 1 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 1.0.0. Answer lives in: the release you run, set against each fixed version. GO-2025-3646 (moderate) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 1 record names k3s with nothing tying it to this repository (CVE-2021-32001).
| 2026-06-03: GHSA-jxr7-mqhw-9p98 (moderate), fixed in 1.33.10: K3s: ZIP Archive Path Traversal Vulnerability in etcd Snapshot Decompression |
| 2025-04-25: GO-2025-3646 (moderate): CNCF K3s Kubernetes kubelet configuration exposes credentials in github.com/k3s-io/k3s |
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 k3s-io/k3s: 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.