Read 2026-10-23
eventual-inc/daft: technical due diligence, read from its repository
What Borehole read in eventual-inc/daft's code and history at 06c1fa2: 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
Architecture & Codebase — including AI provenance
adequatedaft/dataframe/dataframe.py is 6,691 lines, 61× this codebase's median file
adequateThe median source file here is 109 lines. 38 files exceed 1,090 lines, the largest being 6,691. 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.
daft/dataframe/dataframe.py:1 — 6,691 lines (61× median) |
src/daft-recordbatch/src/ops/inline_agg.rs:1 — 3,338 lines (30× median) |
daft/expressions/expressions.py:1 — 3,275 lines (30× median) |
daft/daft/__init__.pyi:1 — 3,008 lines (27× median) |
src/daft-dsl/src/expr/mod.rs:1 — 2,809 lines (25× median) |
9 of 24 notebooks are committed with their outputs
adequate38% of the notebooks carry cell outputs in git, and nothing strips them before commit. Outputs bloat the history, make changes unreadable in review, and carry whatever the cells printed: data, and sometimes keys.
tutorials/delta_lake/1-local-image-batch-inference.ipynb — notebook with outputs |
tutorials/delta_lake/2-distributed-batch-inference.ipynb — notebook with outputs |
tutorials/delta_lake/3-pytorch-ray-single-node-training.ipynb — notebook with outputs |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v0.7.26, is not on the branch this survey read; the newest release on it is v0.7.25. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.7.26 |
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: AWS access key, 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.
tutorials/flyte/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. 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/broken-link-checker.yml:23 — action pinned by tag |
.github/workflows/broken-link-checker.yml:79 — action pinned by tag |
2 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
daft/functions/process.py:30 — command run through a shell |
daft/functions/process.py:64 — command run through a shell |
3 deserialisers that can run code
adequate3 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
daft/execution/udf.py:167 — code-executing deserialiser |
daft/execution/udf.py:174 — code-executing deserialiser |
daft/execution/udf_worker.py:53 — code-executing deserialiser |
36 locked dependencies have published vulnerabilities, 8 high or critical in what ships
adequate36 of 1,490 locked dependencies match 121 published advisories in OSV, 65 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
src/daft-dashboard/frontend/package-lock.json — next 16.2.12: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
uv.lock — certifi 2025.7.14: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19; an optional extra |
uv.lock — pillow 12.3.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0; an optional extra |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 |
1 of 2 deployments run a single replica
adequate1 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
k8s/charts/quickstart/templates/head-deployment.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on eventual-inc/daft: 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.