Read 2026-10-23
koordinator-sh/koordinator: technical due diligence, read from its repository
What Borehole read in koordinator-sh/koordinator's code and history at 949aba5: 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 | adequate |
| 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
README-zh_CN.md:13: names OpenSSF
Architecture & Codebase — including AI provenance
adequatepkg/scheduler/plugins/reservation/plugin.go is 1,682 lines, 11× this codebase's median file
adequateThe median source file here is 149 lines. 2 files exceed 1,490 lines, the largest being 1,682. 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/scheduler/plugins/reservation/plugin.go:1 — 1,682 lines (11× median) |
pkg/scheduler/plugins/elasticquota/core/group_quota_manager.go:1 — 1,506 lines (10× median) |
4 base images float: no version, or `latest`
adequate4 of 12 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
docker/koord-descheduler.dockerfile:21 — base image without a version |
docker/koord-manager.dockerfile:21 — base image without a version |
docker/koord-runtimeproxy.dockerfile:21 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate1,892 unresolved debt markers, 4.0 per thousand lines
adequateThe codebase carries 1,892 TODO, FIXME, HACK or XXX markers across 477,691 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.
apis/analysis/v1alpha1/recommendation_types.go:58 — // TODO add more tuning knobs about aggregation policy |
apis/config/v1alpha1/cluster_colocation_profile_types.go:66 — // TODO: remove this field, use Labels instead. |
apis/configuration/slo_controller_config.go:626 — "Intel(R) Xeon(R) Platinum XXX CPU @ 2.50GHz": { |
apis/extension/qos_utils.go:28 — // TODO: add component options to customize it. |
apis/runtime/v1alpha1/api.pb.go:600 — ContainerEnvs map[string]string `protobuf:"bytes,9,rep,name=container_envs,json=containe |
7 files still carry code deprecated more than two years ago
adequate7 files were marked deprecated over two years ago and still are, the oldest since Mar 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
pkg/client/informers/externalversions/factory.go — deprecated since Mar 2022 |
apis/runtime/v1alpha1/api.pb.go — deprecated since Apr 2022 |
apis/extension/deprecated.go — deprecated since Feb 2023 |
apis/extension/coscheduling.go — deprecated since Aug 2023 |
pkg/scheduler/apis/config/types.go — deprecated since Aug 2023 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate9 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/ci.yaml:21 — action pinned by tag |
.github/workflows/ci.yaml:79 — action pinned by tag |
9 shell commands built from strings
adequate9 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/device-daemon/resource/utils.go:143 — command run through a shell |
pkg/device-daemon/resource/utils.go:210 — command run through a shell |
pkg/device-daemon/resource/utils.go:243 — command run through a shell |
8 locked dependencies have published vulnerabilities, 1 high or critical in what ships
adequate8 of 235 locked dependencies match 14 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.
7 workload settings give a container the host
adequate7 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.
config/manager/koord-device-daemon.yaml:28 — privileged or host namespace |
config/manager/koord-device-daemon.yaml:57 — privileged or host namespace |
config/manager/koord-device-daemon.yaml:58 — 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 4 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/manager/descheduler.yaml — replicas: 1 |
config/manager/scheduler.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 koordinator-sh/koordinator: 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.