Read 2026-10-23
kubero-dev/kubero: technical due diligence, read from its repository
What Borehole read in kubero-dev/kubero's code and history at 11c5abf: 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
MAINTAINERS.md:12: names CNCF
Architecture & Codebase — including AI provenance
strongclient/src/components/apps/form.vue is 2,796 lines, 28× this codebase's median file
adequateThe median source file here is 98 lines. 3 files exceed 1,000 lines, the largest being 2,796. 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.
client/src/components/apps/form.vue:1 — 2,796 lines (28× median) |
server/src/kubernetes/kubernetes.service.ts:1 — 1,495 lines (15× median) |
client/src/components/pipelines/form.vue:1 — 1,084 lines (11× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate17% of bug fixes add or change a test
adequateOf 120 fixes in the last 24 months, 20 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 20 of 120 |
Security & Reliability Posture
adequate1 credential-shaped string committed to the tree
adequateMatches for AWS access key appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. 1 other match set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| AWS access key pattern matched |
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 |
The build runs third-party code it does not pin
adequate12 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/docker-prerelease.yaml:42 — action pinned by tag |
.github/workflows/docker-prerelease.yaml:45 — action pinned by tag |
62 locked dependencies have published vulnerabilities, 92 high or critical
adequate62 of 1,239 locked dependencies match 157 published advisories in OSV, 92 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.
server/yarn.lock — @xhmikosr/decompress 10.2.0: GHSA-hrh2-vp3x-79xf (critical), fixed in 10.2.2 |
server/yarn.lock — form-data 2.3.3: GHSA-fjxv-7rqg-78g4 (critical), fixed in 2.5.4 |
server/yarn.lock — handlebars 4.7.8: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9 |
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.
server/templates/buildpacks.yaml:107 — privileged or host namespace |
server/templates/dockerfile.yaml:98 — privileged or host namespace |
server/templates/nixpacks.yaml:122 — privileged or host namespace |
6 places insert HTML from a variable without sanitising it
adequate6 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
client/src/components/apps/form.vue:232 — HTML from a variable |
client/src/components/apps/form.vue:245 — HTML from a variable |
client/src/components/notifications/index.vue:11 — HTML from a variable |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-16. 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 3.1.1. Answer lives in: the release you run, set against each fixed version.
| 2026-09-16: CVE-2026-92720 (critical): Kubero through 3.1.1 fails to apply authentication guards to the notifications API endpoints, allowing unauthenticated attackers to read webhook secrets and ser |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 514 files for 10 structured logging libraries; 0 matched |
One 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 kubero-dev/kubero: 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.