Read 2026-11-03
openyurtio/openyurt: technical due diligence, read from its repository
What Borehole read in openyurtio/openyurt's code and history at 077652c: 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
GOVERNANCE.md:3: names CNCFREADME.md:9: names OpenSSFREADME.md:19: names Cloud Native Computing Foundation
Architecture & Codebase — including AI provenance
strongpkg/yurtmanager/controller/nodelifecycle/node_life_cycle_controller.go is 1,310 lines, 10× this codebase's median file
adequateThe median source file here is 124 lines. 1 file exceed 1,240 lines, the largest being 1,310. 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/yurtmanager/controller/nodelifecycle/node_life_cycle_controller.go:1 — 1,310 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate573 unresolved debt markers, 3.1 per thousand lines
adequateThe codebase carries 573 TODO, FIXME, HACK or XXX markers across 182,066 lines. These are the team's own notes about work they knew was unfinished. A high density is not automatically bad — it can mean an honest team — but every one of them is a decision deferred, and after an acquisition they are deferred onto someone who was not in the room.
Makefile:205 — # hack/make-rule/generate_openapi.sh // TODO by kadisi |
charts/yurt-iot-dock/crds/iot.openyurt.io_devices.yaml:75 — description: TODO support the following field A list of auto-generated |
charts/yurt-iot-dock/crds/iot.openyurt.io_devices.yaml:86 — empty interface so it can be anything) TODO: location type in edgex |
cmd/yurt-iot-dock/app/core.go:256 — if _, err := client.CoreV1().Namespaces().Get(context.TODO(), opts.Namespace, metav1.GetOp |
cmd/yurt-manager/app/client/token.go:69 — tr, inErr := ts.cli.CoreV1().ServiceAccounts(ts.namespace).CreateToken(context.TODO(), ts. |
Security & Reliability Posture
adequate10 credential-shaped strings 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.
| 5 cited: JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate8 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. 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.
.github/workflows/back-port.yaml:36 — action pinned by tag |
.github/workflows/ci.yaml:31 — action pinned by tag |
2 outbound calls can wait forever
adequate2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
pkg/node-servant/static-pod-upgrade/util/pods.go:70 — outbound call without a timeout |
pkg/yurtadm/util/yurthub/yurthub.go:469 — outbound call without a timeout |
3 shell commands built from strings
adequate3 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
pkg/node-servant/components/kubelet.go:175 — command run through a shell |
pkg/node-servant/components/kubelet.go:180 — command run through a shell |
pkg/yurtadm/util/system/system.go:58 — command run through a shell |
4 locked dependencies have published vulnerabilities, 2 high or critical in what ships
adequate4 of 167 locked dependencies match 6 published advisories in OSV, 2 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.
3 workload settings give a container the host
adequate3 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
charts/yurthub/templates/yurthub-cloud-yurtstaticset.yaml:79 — privileged or host namespace |
charts/yurthub/templates/yurthub-yurtstaticset.yaml:79 — privileged or host namespace |
config/setup/yurthub.yaml:62 — privileged or host namespace |
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 |
2 of 3 deployments run a single replica
adequate2 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
config/setup/raven-proxy-dns.yaml — replicas: 1 |
config/setup/yurt-tunnel-dns.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on openyurtio/openyurt: 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.