Read 2026-11-03
flyteorg/flyte: technical due diligence, read from its repository
What Borehole read in flyteorg/flyte's code and history at 1604356: 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 |
Architecture & Codebase — including AI provenance
adequateflyteidl2/gen_utils/ts/buf/validate/validate_pb.ts is 4,755 lines, 49× this codebase's median file
adequateThe median source file here is 96 lines. 10 files exceed 1,000 lines, the largest being 4,755. 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.
flyteidl2/gen_utils/ts/buf/validate/validate_pb.ts:1 — 4,755 lines (49× median) |
flyteidl2/gen_utils/rust/src/validate.rs:1 — 3,658 lines (38× median) |
runs/service/run_service.go:1 — 2,319 lines (24× median) |
flyteplugins/go/tasks/pluginmachinery/flytek8s/pod_helper.go:1 — 2,054 lines (21× median) |
dataproxy/converter/literal_json_converter.go:1 — 1,937 lines (20× median) |
1 base image floats: no version, or `latest`
adequate1 of 6 `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.
runs/Dockerfile:21 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate97 direct dependencies in a single manifest
adequatego.mod declares 97 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 97 declared |
boilerplate/flyte/golang_support_tools/go.mod — 5 declared |
flyteidl2/gen_utils/python/pyproject.toml — 4 declared |
gen/python/pyproject.toml — 4 declared |
Security & Reliability Posture
adequate2 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 |
runs/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate17 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; 1 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.
.github/workflows/build-ci-image.yml:60 — action pinned by tag |
.github/workflows/build-ci-image.yml:64 — action pinned by tag |
flytestdlib/godownloader.sh:42 — download piped into a shell |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-10-11. 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 2.0.53. Answer lives in: the release you run, set against each fixed version.
| 2026-10-11: CVE-2026-108728 (high): Flyte 2.0.1 through 2.0.51 contains a cleartext secret storage vulnerability that allows users with Pod read access to obtain secrets by reading init container |
Observability & Operations
adequateReadiness and liveness probes are identical in 3 of 13 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.
charts/flyte-binary/templates/console/deployment.yaml — same probe endpoint twice |
charts/flyte-binary/templates/deployment.yaml — same probe endpoint twice |
charts/flyte-core/templates/console/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 flyteorg/flyte: 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.