Read 2026-10-04
kestra-io/kestra: technical due diligence, read from its repository
What Borehole read in kestra-io/kestra's code and history at b6282f6: 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 | 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
Architecture & Codebase — including AI provenance
strongui/packages/design-system/src/components/Data/KsDataTable/KsFilter.locale.ts is 5,216 lines, 77× this codebase's median file
adequateThe median source file here is 67 lines. 19 files exceed 1,000 lines, the largest being 5,216. 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.
ui/packages/design-system/src/components/Data/KsDataTable/KsFilter.locale.ts:1 — 5,216 lines (77× median) |
webserver/src/main/java/io/kestra/webserver/controllers/api/ExecutionController.java:1 — 3,012 lines (44× median) |
executor/src/main/java/io/kestra/executor/ExecutorService.java:1 — 1,889 lines (28× median) |
core/src/main/java/io/kestra/core/services/ExecutionService.java:1 — 1,473 lines (21× median) |
ui/src/components/inputs/LowCodeEditor.vue:1 — 1,452 lines (21× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e/playwright.config.ts); 1 test is individually marked to retry. A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
e2e/playwright.config.ts:38 — test retry |
core/src/test/java/io/kestra/core/models/tasks/retrys/RandomTest.java:32 — test retry |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v2.0.4, is not on the branch this survey read; the newest release on it is v0.19.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.0.4 |
Security & Reliability Posture
adequate1 credential-shaped string 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.
| private key block, where fakes are usual |
The build runs third-party code it does not pin
adequate18 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/e2e-scheduling.yml:23 — action pinned by tag |
.github/workflows/e2e-scheduling.yml:39 — action pinned by tag |
1 of 1 Kubernetes workloads declare no resource limits
adequate1 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.
charts/kestra-starter/templates/statefulset.yaml — workload with no limits |
9 locked dependencies have published vulnerabilities, 15 high or critical in what ships
adequate9 of 766 locked dependencies match 42 published advisories in OSV, 22 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.
ui/package-lock.json — axios 1.18.1: GHSA-3pq3-5fj3-cg6v (high), fixed in 1.20.0 |
ui/package-lock.json — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10 |
ui/package-lock.json — fast-uri 3.1.5: GHSA-5jgf-p345-68v8 (high), fixed in 3.1.6 |
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.
charts/kestra/values.yaml:344 — privileged or host namespace |
charts/kestra/values.yaml:358 — privileged or host namespace |
docker-compose-dind.yml:33 — privileged or host namespace |
54 places insert HTML from a variable without sanitising it
adequate54 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.
ui/packages/design-system/src/components/Data/KsDataTable/KsBulkSelect.vue:8 — HTML from a variable |
ui/packages/design-system/src/components/Data/KsDataTable/KsBulkSelect.vue:16 — HTML from a variable |
ui/packages/design-system/src/components/Data/KsEmpty.vue:9 — HTML from a variable |
32 advisories against this project in the last 24 months, 18 high or critical, 1 on CISA's known-exploited list
adequate1 of them is on CISA's known-exploited list: check first whether the release you run has the fix. The newest was published on 2026-09-29. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| 2026-06-03: GHSA-5vc5-wxxq-3fjx (critical; on CISA's Known Exploited list), fixed in 1.0.45: Unauthenticated Remote Code Execution via Authentication Bypass in `AuthenticationFilter` |
| 2026-09-29: GHSA-xh2h-59mw-8qr2 (moderate), fixed in 1.3.40: Deleted namespace file content remains readable via the revision parameter |
| 2026-09-29: GHSA-hrr4-xg8h-5p6f (high), fixed in 2.0.3: Unauthenticated gRPC control plane on port 50051 exposes and mutates KV/namespace metadata and worker jobs |
| 2026-09-29: GHSA-g769-pv29-qhff (moderate), fixed in 2.0.2: Possible HTTP allowed-list regression introduced in commit 0354ddf8 |
| 2026-09-29: GHSA-9gp7-896w-m3r7 (low), fixed in 2.0.1: Content-Disposition filename parameter injection in Kestra via an unvalidated `namespace` path segment on the namespace-files export endpoint |
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 5,237 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 |
2 of 6 deployed images carry no version, or `latest`
adequate2 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.
docker-compose-ci.yml:3 — image without a version |
docker-compose-dind.yml:45 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on kestra-io/kestra: 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.