Read 2026-10-04
jgm/pandoc: technical due diligence, read from its repository
What Borehole read in jgm/pandoc's code and history at 30bad89: 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 | not assessable |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongsrc/Text/Pandoc/Writers/Powerpoint/Output.hs is 3,068 lines, 17× this codebase's median file
adequateThe median source file here is 175 lines. 5 files exceed 1,750 lines, the largest being 3,068. 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/Text/Pandoc/Writers/Powerpoint/Output.hs:1 — 3,068 lines (17× median) |
src/Text/Pandoc/Readers/Markdown.hs:1 — 2,413 lines (13× median) |
src/Text/Pandoc/Readers/RST.hs:1 — 1,962 lines (11× median) |
src/Text/Pandoc/Writers/HTML.hs:1 — 1,892 lines (10× median) |
src/Text/Pandoc/Readers/LaTeX/Parsing.hs:1 — 1,888 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
not assessableThe build runs third-party code it does not pin
adequate4 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. 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/nightly.yml:111 — action pinned by tag |
.github/workflows/nightly.yml:114 — action pinned by tag |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,805 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,805 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 jgm/pandoc: 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.