Read 2026-10-23
neuml/txtai: technical due diligence, read from its repository
What Borehole read in neuml/txtai's code and history at 738aac4: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate33% of commit subjects are exact repeats of another subject, and subject length varies by only 24.1 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 129× 'Update documentation' |
| 94× 'Update build script' |
| 67× 'Bump version' |
src/python/txtai/embeddings/base.py is 1,112 lines, 15× this codebase's median file
adequateThe median source file here is 74 lines. 1 file exceed 1,000 lines, the largest being 1,112. 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.
src/python/txtai/embeddings/base.py:1 — 1,112 lines (15× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
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.
| Slack token, where fakes are usual |
6 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.
docker/api/Dockerfile — runs as root |
docker/aws/Dockerfile — runs as root |
docker/base/Dockerfile — runs as root |
docker/minimal/Dockerfile — runs as root |
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.
src/python/txtai/serialize/pickle.py:54 — code-executing deserialiser |
src/python/txtai/serialize/pickle.py:63 — code-executing deserialiser |
2 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-06-30. 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 9.14.0. Answer lives in: the release you run, set against each fixed version.
| 2026-06-30: CVE-2026-58449 (critical): txtai through 9.10.0, fixed in commit 11b32da, exposes an API /reindex endpoint whose function body parameter is resolved through txtai.util.Resolver, which per |
| 2025-09-22: CVE-2025-10854 (high): The txtai framework allows the loading of compressed tar files as embedding indices. While the validate function is intended to prevent path traversal vulnerabi |
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 neuml/txtai: 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.