Borehole · Project · free tier
ucbepic/docetl
Free reading: not for reliance
53d292e · 921 commits · 515 files
Read 2026-11-03

ucbepic/docetl: technical due diligence, read from its repository

What Borehole read in ucbepic/docetl's code and history at 53d292e: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.3

Commit messages are templated rather than written

adequate

31% of commit subjects are exact repeats of another subject, and subject length varies by only 19.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.

Evidence
11× 'Update docs'
9× 'Update todos'
8× 'chore: bump up version'
01.6

website/src/components/operations/components.tsx is 2,459 lines, 12× this codebase's median file

adequate

The median source file here is 190 lines. 2 files exceed 1,900 lines, the largest being 2,459. 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.

Evidence
website/src/components/operations/components.tsx:1 — 2,459 lines (12× median)
docetl/optimizers/reduce_optimizer.py:1 — 1,916 lines (10× median)

Engineering Process & SDLC Maturity

adequate
02.24

7% of recent commits change more than 2,000 lines

adequate

20 of 293 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.

Evidence
20 commits over 2,000 lines

Product & Engineering Maturity

adequate
04.17

Node.js 20 is past end of life

adequate

The code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.

Evidence
Dockerfile — Node.js 20, end of life 2026-04-30
04.19

16% of bug fixes add or change a test

adequate

Of 83 fixes in the last 24 months, 13 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.

Evidence
13 of 83

Security & Reliability Posture

adequate
05.6

1 Dockerfile runs the application as root

adequate

No 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.

Evidence
Dockerfile — runs as root
05.27

The build runs third-party code it does not pin

adequate

2 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; 5 steps pipe a download straight into a shell. 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.

Evidence
.github/workflows/release.yml:49 — action pinned by tag
.github/workflows/stage.yml:38 — action pinned by tag
.github/workflows/ci.yml:30 — download piped into a shell
05.13

2 outbound calls can wait forever

adequate

2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.

Evidence
docetl/operations/map.py:423 — outbound call without a timeout
docetl/operations/map.py:888 — outbound call without a timeout
05.48

5 places insert HTML from a variable without sanitising it

adequate

5 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.

Evidence
website/src/components/AnsiRenderer.tsx:72 — HTML from a variable
website/src/components/SearchableCell.tsx:148 — HTML from a variable
website/src/components/SearchableCell.tsx:158 — HTML from a variable

Observability & Operations

adequate
06.2

No structured logging library is in use

adequate

Nothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.

Evidence
searched 471 files for 10 structured logging libraries; 0 matched
06.8

One request cannot be followed through the logs

adequate

Nothing 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.

Evidence
no request id, correlation id or tracing found
06.9

No error reporter is wired in

adequate

Nothing 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.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on ucbepic/docetl: 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.