Read 2026-11-03
docling-project/docling: technical due diligence, read from its repository
What Borehole read in docling-project/docling's code and history at bffc365: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
.github/SECURITY.md:11: names OpenSSF
Architecture & Codebase — including AI provenance
adequatedocling/backend/html_backend.py is 5,552 lines, 27× this codebase's median file
adequateThe median source file here is 200 lines. 10 files exceed 2,000 lines, the largest being 5,552. 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.
docling/backend/html_backend.py:1 — 5,552 lines (27× median) |
docling/backend/msword_backend.py:1 — 5,132 lines (25× median) |
docling/backend/msexcel_backend.py:1 — 2,916 lines (14× median) |
docling/backend/opendocument_backend.py:1 — 2,678 lines (13× median) |
docling/datamodel/pipeline_options.py:1 — 2,488 lines (12× median) |
1 base image floats: no version, or `latest`
adequate1 of 3 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
.actor/Dockerfile:23 — base image without a version |
Engineering Process & SDLC Maturity
adequate6% of recent commits change more than 2,000 lines
adequate90 of 1411 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.
| 90 commits over 2,000 lines |
Product & Engineering Maturity
strongNode.js 20 is past end of life
adequateThe 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.
.actor/Dockerfile — Node.js 20, end of life 2026-04-30 |
Security & Reliability Posture
adequate1 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.
Dockerfile — runs as root |
6 locked dependencies have published vulnerabilities, 30 high or critical in what ships
adequate6 of 427 locked dependencies match 65 published advisories in OSV, 30 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.
35 advisories against this project in the last 24 months, 10 high or critical
adequateThe newest was published on 2026-10-23. 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 5 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 2.146.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 3 records name docling with nothing tying them to this repository (CVE-2026-78163, CVE-2026-95628, CVE-2026-95629).
| 2026-10-23: GHSA-cvvj-vhrh-gxp9 (moderate), fixed in 2.142.1: Format detection reads the ZIP mimetype member without a size limit, so a small archive can exhaust memory |
| 2026-10-23: GHSA-h8jf-9f4f-2v9h (moderate), fixed in 2.142.1: Tectonic TikZ pre-check can be bypassed, allowing arbitrary file read and write |
| 2026-10-23: GHSA-m5xp-wvrj-48wx (moderate), fixed in 2.142.1: Image backend decodes every frame before max_num_pages applies, so a small multi-frame image can exhaust memory |
| 2026-10-23: GHSA-969p-q7h6-6fr8 (moderate), fixed in 2.142.1: DOCX and XLSX backends decompress archive members without an effective size limit, so a small file can exhaust memory |
| 2026-10-23: GHSA-c2w9-g7hj-xcr8 (moderate), fixed in 2.142.1: AsciiDoc inline-format regex is quadratic in paragraph length (CPU exhaustion) |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,413 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 1,413 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 |
No structured logging library is in use
adequateNothing 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.
| searched 1,413 files for 10 structured logging libraries; 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 docling-project/docling: 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.