Read 2026-10-04
libvips/libvips: technical due diligence, read from its repository
What Borehole read in libvips/libvips's code and history at 666222d: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:100: The project does not take pull requestsCONTRIBUTING.md:98: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongcplusplus/include/vips/VImage8.h is 6,895 lines, 27× this codebase's median file
adequateThe median source file here is 250 lines. 9 files exceed 2,500 lines, the largest being 6,895. 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.
cplusplus/include/vips/VImage8.h:1 — 6,895 lines (27× median) |
libvips/deprecated/vips7compat.c:1 — 5,912 lines (23× median) |
cplusplus/vips-operators.cpp:1 — 4,174 lines (16× median) |
libvips/iofuncs/image.c:1 — 3,994 lines (15× median) |
libvips/foreign/tiff2vips.c:1 — 3,562 lines (14× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate36 test files against 604 source files (6.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.
| 36 test files / 604 source files |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.50 to 0.79 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.50, second half 0.79 (split 2017-03-15) |
13% of bug fixes add or change a test
adequateOf 119 fixes in the last 24 months, 16 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.
| 16 of 119 |
Security & Reliability Posture
adequateThe 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/cifuzz.yml:32 — action pinned by tag |
.github/workflows/cifuzz.yml:37 — action pinned by tag |
21 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-09-24. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. The record is incomplete: NVD: 1 record names libvips with nothing tying it to this repository (CVE-2026-66066).
| 2026-09-24: CVE-2026-88360 (unrated): libvips 8.19.0 contains a memory access vulnerability when processing little-endian PFM images. If the PFM text header length is not a multiple of four bytes, t |
| 2026-08-14: GHSA-h27h-jf9v-m8rg (low), fixed in >= 8.18.3: Possible heap-based buffer read overflow when resizing and re-encoding a JPEG with gain map |
| 2026-08-14: GHSA-fh99-55jf-5hj3 (moderate), fixed in >= 8.18.3: Possible heap-based buffer read overflow when decoding a well-crafted RLE Radiance image |
| 2026-08-14: GHSA-rjmm-3qch-m9rg (moderate), fixed in >= 8.18.3: A well-crafted PPM image processed via a custom source could lead to possible heap buffer write overflow |
| 2026-08-14: GHSA-7p29-wg2h-36q4 (moderate), fixed in >= 8.18.3: Possible integer overflow when reading multi-page TIFF images via ImageMagick |
Observability & Operations
not assessableNot rated: only 4 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 libvips/libvips: 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.