Read 2026-10-28
strimzi/strimzi-kafka-operator: technical due diligence, read from its repository
What Borehole read in strimzi/strimzi-kafka-operator's code and history at 9ab67e9: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
README.md:5: names OpenSSFREADME.md:36: names CNCFREADME.md:169: names Cloud Native Computing Foundation
Architecture & Codebase — including AI provenance
adequateoperator-common/src/main/java/io/strimzi/operator/common/ReconciliationLogger.java is 8,459 lines, 83× this codebase's median file
adequateThe median source file here is 101 lines. 7 files exceed 1,010 lines, the largest being 8,459. 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.
operator-common/src/main/java/io/strimzi/operator/common/ReconciliationLogger.java:1 — 8,459 lines (83× median) |
cluster-operator/src/main/java/io/strimzi/operator/cluster/model/KafkaCluster.java:1 — 2,115 lines (20× median) |
cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/assembly/KafkaRebalanceAssemblyOperator.java:1 — 1,473 lines (14× median) |
crd-generator/src/main/java/io/strimzi/crdgenerator/CrdGenerator.java:1 — 1,329 lines (13× median) |
cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/assembly/AbstractConnectOperator.java:1 — 1,295 lines (12× median) |
11 base images float: no version, or `latest`
adequate11 of 11 `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-images/base/Dockerfile:4 — base image without a version |
docker-images/base/Dockerfile:9 — base image without a version |
docker-images/base/Dockerfile:78 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.49 to 0.76 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.49, second half 0.76 (split 2021-08-01) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 1.3.0, is not on the branch this survey read; the newest pre-release on it is 0.1.0-rc3. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 1.3.0 |
Security & Reliability Posture
adequate3 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.
| 3 cited: private key block, where fakes are usual |
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.
docker-images/base/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate1 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 4 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.
.github/workflows/osps-baseline.yml:54 — action pinned by tag |
.github/workflows/github-actions-integration.yml:56 — download piped into a shell |
5 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-06-17. 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 3 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version.
| 2026-06-17: GHSA-r427-j2h7-wv3m (moderate), fixed in 1.0.1: Unrestricted access to all Secrets within namespace watched by the Topic operator |
| 2026-06-17: GHSA-mw9r-p8xp-wx96 (high), fixed in 1.0.1: Cross-namespace privilege escalation via `Kafka.spec.entityOperator` |
| 2026-02-19: GHSA-2qwx-rq6j-8r6j (high), fixed in 0.50.1: All CAs from a custom CA chain consisting of multiple CAs are trusted for mTLS user authentication |
| 2026-02-19: GHSA-6x85-j2f7-4xc5 (moderate), fixed in 0.50.1: All CAs from CA chain will be trusted in Kafka Connect and Kafka MirrorMaker 2 target clusters |
| 2025-12-05: GHSA-xrhh-hx36-485q (high), fixed in 0.49.1: Unrestricted access to all Secrets in the same Kubernetes namespace from Kafka Connect and MirrorMaker 2 operands |
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 2,233 files for 10 structured logging libraries; 0 matched |
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 |
Readiness and liveness probes are identical in 6 of 16 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
install/drain-cleaner/certmanager/060-Deployment.yaml — same probe endpoint twice |
install/drain-cleaner/kubernetes/060-Deployment.yaml — same probe endpoint twice |
install/drain-cleaner/openshift/060-Deployment.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on strimzi/strimzi-kafka-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.