Read 2026-10-28
dlt-hub/dlt: technical due diligence, read from its repository
What Borehole read in dlt-hub/dlt's code and history at e914711: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:12: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongdlt/pipeline/pipeline.py is 2,260 lines, 20× this codebase's median file
adequateThe median source file here is 108 lines. 15 files exceed 1,080 lines, the largest being 2,260. 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.
dlt/pipeline/pipeline.py:1 — 2,260 lines (20× median) |
dlt/common/libs/pyarrow.py:1 — 1,814 lines (16× median) |
dlt/destinations/impl/filesystem/filesystem.py:1 — 1,730 lines (16× median) |
dlt/common/schema/utils.py:1 — 1,616 lines (14× median) |
dlt/destinations/sql_jobs.py:1 — 1,556 lines (14× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (.github/workflows/test_destinations_remote.yml). 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/test_destinations_remote.yml:72 — test retry |
5% of recent commits change more than 2,000 lines
adequate51 of 1016 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.
| 51 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 1.31.0, is not on the branch this survey read; the newest release on it is 1.30.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 1.31.0 |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 2,139 tracked files; 0 present |
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.
deploy/dlt/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 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/agentic-docs.yml:158 — action pinned by tag |
.github/workflows/agentic-docs.yml:165 — action pinned by tag |
2 deserialisers that can run code
adequate2 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.
dlt/helpers/marimo/utils.py:17 — code-executing deserialiser |
dlt/pipeline/trace.py:352 — code-executing deserialiser |
44 locked dependencies have published vulnerabilities, 18 high or critical in what ships
adequate44 of 515 locked dependencies match 151 published advisories in OSV, 84 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.
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on dlt-hub/dlt: 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.