Read 2026-10-04
prefecthq/prefect: technical due diligence, read from its repository
What Borehole read in prefecthq/prefect's code and history at 4f52bc6: 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
.github/pull_request_template.md:8: states a policy on AI-generated contributions.gitmodules:1: 1 submodule(s) this survey does not read: compat-tests
Architecture & Codebase — including AI provenance
strongui-v2/src/api/prefect.ts is 19,339 lines, 207× this codebase's median file
adequateThe median source file here is 93 lines. 65 files exceed 1,000 lines, the largest being 19,339. 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-v2/src/api/prefect.ts:1 — 19,339 lines (207× median) |
src/integrations/prefect-databricks/prefect_databricks/models/jobs.py:1 — 4,428 lines (47× median) |
src/prefect/flows.py:1 — 3,699 lines (39× median) |
src/integrations/prefect-github/prefect_github/repository.py:1 — 3,446 lines (37× median) |
src/prefect/server/schemas/filters.py:1 — 2,566 lines (27× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (.github/workflows/integration-package-tests.yaml). 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.
.github/workflows/integration-package-tests.yaml:127 — test retry |
Product & Engineering Maturity
strong11 files still carry code deprecated more than two years ago
adequate11 files were marked deprecated over two years ago and still are, the oldest since Jun 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
src/prefect/task_runners.py — deprecated since Jun 2022 |
src/prefect/docker/__init__.py — deprecated since Jun 2022 |
src/prefect/logging/configuration.py — deprecated since Nov 2022 |
src/prefect/utilities/annotations.py — deprecated since Jan 2023 |
src/prefect/_internal/compatibility/deprecated.py — deprecated since Feb 2023 |
Security & Reliability Posture
adequate4 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. 2 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 4 cited: private key block, where fakes are usual |
5 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 |
client/Dockerfile — runs as root |
src/integrations/prefect-aws/Dockerfile — runs as root |
src/integrations/prefect-azure/Dockerfile — runs as root |
1 environment file is committed
adequateui-v2/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
ui-v2/.env — committed environment file |
The build runs third-party code it does not pin
adequate16 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/benchmarks.yaml:41 — action pinned by tag |
.github/workflows/benchmarks.yaml:110 — action pinned by tag |
15 locked dependencies have published vulnerabilities, 6 high or critical in what ships
adequate15 of 1,087 locked dependencies match 59 published advisories in OSV, 21 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.
uv.lock — pyjwt 2.13.0: GHSA-ffc3-869f-jxw9 (critical), fixed in 2.14.0; an optional extra |
uv.lock — urllib3 2.7.0: GHSA-8988-9cw3-xx77 (high), fixed in 2.8.0 |
ui-v2/package-lock.json — lodash-es 4.17.23: GHSA-r5fr-rjxr-66jc (high), fixed in 4.18.0 |
8 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-08-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 3.8.7. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 2 records name prefect with nothing tying them to this repository (CVE-2026-3515, CVE-2026-5366).
| 2026-08-11: CVE-2026-72538 (high): An argument injection vulnerability in PrefectHQ Prefect through 3.8.2 allows authenticated users to achieve remote code execution via the git_clone pull step b |
| 2026-06-02: GHSA-c635-393c-hcx2 (high), fixed in 3.6.22.dev7: Prefect has an Authentication Middleware Bypass when URL paths are appended with 'health' or 'ready' |
| 2026-05-26: GHSA-cw25-2p92-7f75 (high): Prefect has an Argument Injection issue |
| 2026-05-04: GHSA-6rcx-55r6-jx65 (low), fixed in 3.6.25.dev7: Prefect Git Argument Injection in GitRepository Pull Steps |
| 2026-05-04: GHSA-6rr6-v7cj-mxpg (moderate), fixed in 3.6.22: Prefect Auth Bypass via endswith() Health Check Exemption |
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 4,005 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on prefecthq/prefect: 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.