Read 2026-11-03
truera/trulens: technical due diligence, read from its repository
What Borehole read in truera/trulens's code and history at 915e3ab: 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 |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: AGPL-3.0 → MIT (2023-05-16)CONTRIBUTING.md:176: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/feedback/trulens/feedback/llm_provider.py is 5,559 lines, 62× this codebase's median file
adequateThe median source file here is 89 lines. 21 files exceed 1,000 lines, the largest being 5,559. 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/feedback/trulens/feedback/llm_provider.py:1 — 5,559 lines (62× median) |
src/core/trulens/core/database/sqlalchemy.py:1 — 3,408 lines (38× median) |
src/core/trulens/core/app.py:1 — 2,382 lines (26× median) |
src/core/trulens/core/session.py:1 — 2,181 lines (24× median) |
src/core/trulens/core/run.py:1 — 1,981 lines (22× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, trulens-2.16.0, is not on the branch this survey read; the newest release on it is trulens-2.12.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag trulens-2.16.0 |
Security & Reliability Posture
adequate1 deserialiser that can run code
adequate1 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/core/trulens/core/schema/app.py:277 — code-executing deserialiser |
24 locked dependencies have published vulnerabilities, 30 high or critical in what ships
adequate24 of 625 locked dependencies match 123 published advisories in OSV, 62 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.
poetry.lock — certifi 2026.7.22: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
poetry.lock — pillow 12.3.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0 |
poetry.lock — litellm 1.80.0: GHSA-4xpc-pv4p-pm3w (critical), fixed in 1.84.0; a development dependency |
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 truera/trulens: 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.