Read 2026-11-03
run-llama/liteparse: technical due diligence, read from its repository
What Borehole read in run-llama/liteparse's code and history at db276d5: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongcrates/liteparse/src/markdown_layout/tables.rs is 7,740 lines, 43× this codebase's median file
adequateThe median source file here is 180 lines. 8 files exceed 1,800 lines, the largest being 7,740. 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.
crates/liteparse/src/markdown_layout/tables.rs:1 — 7,740 lines (43× median) |
crates/liteparse/src/projection.rs:1 — 5,952 lines (33× median) |
crates/liteparse/src/extract.rs:1 — 4,935 lines (27× median) |
crates/liteparse/src/ocr_merge.rs:1 — 3,403 lines (18× median) |
crates/pdfium-sys/bindings.rs:1 — 3,317 lines (18× median) |
Engineering Process & SDLC Maturity
adequate28% of commit subjects say nothing about the change
adequate253 of 905 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 253/905 low-content subjects (28.0%) |
| 'format' |
| 'README' |
| 'lock' |
| 'add script' |
Product & Engineering Maturity
adequate18% of bug fixes add or change a test
adequateOf 200 fixes in the last 24 months, 36 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.
| 36 of 200 |
Security & Reliability Posture
adequate5 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.
Dockerfile — runs as root |
ocr/easyocr/Dockerfile — runs as root |
ocr/indraocr/Dockerfile — runs as root |
ocr/paddleocr/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate5 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; 2 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.
.github/workflows/ci-node.yml:75 — action pinned by tag |
.github/workflows/ci-python.yml:92 — action pinned by tag |
scripts/build-musl-node.sh:18 — download piped into a shell |
1 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.
packages/python/liteparse/_pool.py:63 — code-executing deserialiser |
16 locked dependencies have published vulnerabilities, 11 high or critical in what ships
adequate16 of 736 locked dependencies match 47 published advisories in OSV, 13 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Cargo.lock — zip 2.4.2: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
dataset_eval_utils/uv.lock — pypdf 6.21.2: GHSA-42gh-23hr-vphw (high), fixed in 6.21.3 |
ocr/suryaocr/uv.lock — transformers 4.57.6: GHSA-29pf-2h5f-8g72 (high), fixed in 5.3.0 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 234 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 234 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
One request cannot be followed through the logs
adequateNothing 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.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing 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.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on run-llama/liteparse: 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.