Read 2026-10-23
deepset-ai/haystack: technical due diligence, read from its repository
What Borehole read in deepset-ai/haystack's code and history at 76fc2d3: 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:20: states a policy on AI-generated contributionsREADME.md:8: names OpenSSF
Architecture & Codebase — including AI provenance
stronghaystack/core/pipeline/base.py is 1,992 lines, 12× this codebase's median file
adequateThe median source file here is 157 lines. 1 file exceed 1,570 lines, the largest being 1,992. 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.
haystack/core/pipeline/base.py:1 — 1,992 lines (12× median) |
Engineering Process & SDLC Maturity
adequate7% of recent commits change more than 2,000 lines
adequate175 of 2557 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.
| 175 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v3.4.1, is not on the branch this survey read; the newest release on it is v1.8.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v3.4.1 |
Security & Reliability Posture
adequate12 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
docs-website/package.json:28 — ^3.0.0 |
docs-website/package.json:29 — ^5.0.6 |
docs-website/package.json:30 — ^24.0.3 |
docs-website/package.json:31 — ^2.0.0 |
docs-website/package.json:32 — ^0.0.1 |
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.
.clusterfuzzlite/Dockerfile — runs as root |
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
haystack/marshal/yaml.py:40 — code-executing deserialiser |
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 deepset-ai/haystack: 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.