Read 2026-11-03
kube-logging/logging-operator: technical due diligence, read from its repository
What Borehole read in kube-logging/logging-operator's code and history at cab10ab: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:52: states a policy on AI-generated contributionsREADME.md:6: names CNCF
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 2,373,344 lines — 77% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2018-06-23T04:31:31+00:00; +2,373,344 across 6405 files; subject: 'INITIAL COMMIT' |
1 base image floats: no version, or `latest`
adequate1 of 14 `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.
images/config-reloader/Dockerfile:23 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate4 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 |
images/config-reloader/Dockerfile — runs as root |
images/fluentd-drain-watch/Dockerfile — runs as root |
images/syslog-ng-reloader/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate1 step pipes 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.
.claude/hooks/security-bash.sh:31 — download piped into a shell |
1 locked dependency has published vulnerabilities, 1 high or critical
adequate1 of 313 locked dependencies match 1 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. None of the high or critical ones is in what the product ships: some are pinned to a commit or a branch.
pkg/sdk/go.mod — github.com/kube-logging/logging-operator v0.0.0-20260525191431-270b64e8120f: GHSA-mjqf-28ph-426h (critical); pinned to a commit or a branch, so whether it has the fix needs the dependency's own source |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-06-08. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 1 record names logging-operator with nothing tying it to this repository (CVE-2026-10609).
| 2026-06-08: GHSA-mjqf-28ph-426h (critical), fixed in 0.0.0-20260608145523-cf437d7f1e05: Logging operator has Fluentd configuration injection that allows remote code execution |
Observability & Operations
strongNo 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 |
1 of 2 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
charts/logging-operator/values.yaml:348 — image without a version |
1 of 7 deployments run a single replica
adequate1 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/manager.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 kube-logging/logging-operator: 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.