Borehole · Project · free tier
kgateway-dev/kgateway
Free reading: not for reliance
35b6be5 · 5,470 commits · 2,812 files
Read 2026-10-23

kgateway-dev/kgateway: technical due diligence, read from its repository

What Borehole read in kgateway-dev/kgateway's code and history at 35b6be5: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsstrong
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed
  • README.md:20: names OpenSSF
  • README.md:85: names Cloud Native Computing Foundation

Architecture & Codebase — including AI provenance

strong
01.6

pkg/krtcollections/policy.go is 1,935 lines, 14× this codebase's median file

adequate

The median source file here is 137 lines. 2 files exceed 1,370 lines, the largest being 1,935. 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.

Evidence
pkg/krtcollections/policy.go:1 — 1,935 lines (14× median)
pkg/kgateway/translator/listener/gateway_listener_translator.go:1 — 1,467 lines (10× median)

Engineering Process & SDLC Maturity

adequate
02.24

7% of recent commits change more than 2,000 lines

adequate

121 of 1827 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.

Evidence
121 commits over 2,000 lines

Product & Engineering Maturity

strong
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v2.4.7, is not on the branch this survey read; the newest release on it is v2.1.0. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v2.4.7

Security & Reliability Posture

adequate
05.1

23 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings

adequate

Strings 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.

Evidence
5 cited: private key block, where fakes are usual
05.6

2 Dockerfiles run the application as root

adequate

No 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.

Evidence
.oss-scanner/Dockerfile — runs as root
internal/envoy_modules/Dockerfile — runs as root
05.27

The build runs third-party code it does not pin

adequate

2 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.

Evidence
.oss-scanner/Dockerfile:28 — download piped into a shell
05.34

2 of 2 Kubernetes workloads declare no resource limits

adequate

2 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.

Evidence
install/helm/kgateway/templates/deployment.yaml — workload with no limits
pkg/kgateway/helm/envoy/templates/deployment.yaml — workload with no limits
05.26

1 locked dependency has published vulnerabilities, 4 high or critical

adequate

1 of 506 locked dependencies match 5 published advisories in OSV, 4 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: the project marks 4 as not affecting it, with its reason beside the reference; some are pinned to a commit or a branch.

Evidence
go.mod — istio.io/istio v0.0.0-20260605182440-f18fd540c0e8: GHSA-7774-7vr3-cc8j (high); pinned to a commit or a branch, so whether it has the fix needs the dependency's own source
05.65

5 advisories against this project in the last 24 months, 1 high or critical

adequate

The newest was published on 2026-09-01. 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: its version is only known to be at least 2.1.0. Answer lives in: the release you run, set against each fixed version.

Evidence
2026-09-01: GHSA-qxh6-6qr5-cmv3 (moderate), fixed in v2.3.8: SDS gRPC server binds 0.0.0.0:8234 with no authentication and serves the gateway's Istio mTLS private key; any pod on the cluster network can exfiltrate it (ide
2026-08-11: GHSA-36fr-64g3-wqx4 (moderate), fixed in 2.2.7: kgateway OAuth2 GatewayExtension cross-namespace ReferenceGrant bypass
2025-11-04: GHSA-4766-x535-jw3r (moderate), fixed in 2.0.5: kgateway is missing xDS authorization
2025-11-04: GHSA-5pmx-7r6r-wfqq (moderate), fixed in 2.0.5: Kgateway transformation policy template can emit files from the container
2025-07-24: GHSA-49gr-cc65-hxgw (critical): Command injection via `issue_comment` in GitHub Action

Observability & Operations

strong
06.9

No error reporter is wired in

adequate

Nothing 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.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on kgateway-dev/kgateway: 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.