Read 2026-11-07
wmjordan/pdfpatcher: technical due diligence, read from its repository
What Borehole read in wmjordan/pdfpatcher's code and history at e8c720a: 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 | not assessable |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 189,999 lines — 69% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2021-12-24T12:35:03+00:00; +189,999 across 633 files; subject: 'PDF补丁丁公开源代码' |
App/Functions/Editor/ViewerControl.cs is 1,349 lines, 18× this codebase's median file
adequateThe median source file here is 73 lines. 4 files exceed 1,000 lines, the largest being 1,349. 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.
App/Functions/Editor/ViewerControl.cs:1 — 1,349 lines (18× median) |
App/Common/CustomButton/GlassButton.cs:1 — 1,335 lines (18× median) |
App/Common/FilePath.cs:1 — 1,057 lines (14× median) |
App/Processor/Worker.cs:1 — 1,044 lines (14× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 4 of 122 commits (3.3%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 4 of 122 commits in the last 24 months carry review evidence; 11.3% across all 513 |
Tests are absent or token
adequate0 test files against 325 source files (0.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 0 test files / 325 source files |
Product & Engineering Maturity
not assessableEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.05 to 1.03 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.05, second half 1.03 (split 2024-05-18) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.1.3, is not on the branch this survey read; the newest release on it is v1.1.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.1.3 |
Security & Reliability Posture
strong2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2025-11-17. 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 2 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 1.1.1. Answer lives in: the release you run, set against each fixed version.
| 2025-11-17: CVE-2025-63917 (high): PDFPatcher thru 1.1.3.4663 executable's XML bookmark import functionality does not restrict XML external entity (XXE) references. The application uses .NET's Xm |
| 2025-11-17: CVE-2025-63918 (moderate): PDFPatcher executable does not validate user-supplied file paths, allowing directory traversal attacks allowing attackers to upload arbitrary files to arbitrary |
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 wmjordan/pdfpatcher: 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.