Read 2026-10-04
madler/zlib: technical due diligence, read from its repository
What Borehole read in madler/zlib's code and history at 767c4c9: 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 |
Architecture & Codebase — including AI provenance
strongcrc32.h is 9,447 lines, 39× this codebase's median file
adequateThe median source file here is 238 lines. 1 file exceed 2,380 lines, the largest being 9,447. 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.
crc32.h:1 — 9,447 lines (39× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate8 test files against 113 source files (7.1%). 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.
| 8 test files / 113 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 271 tracked files |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.58 to 0.85 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.58, second half 0.85 (split 2019-01-24) |
15% of bug fixes add or change a test
adequateOf 55 fixes in the last 24 months, 8 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.
| 8 of 55 |
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 271 tracked files; 0 present |
The build runs third-party code it does not pin
adequate11 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/fuzz.yml:8 — action pinned by tag |
.github/workflows/fuzz.yml:14 — action pinned by tag |
4 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-09-03. 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 3 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.3.2. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 36 records name zlib with nothing tying them to this repository (CVE-2002-0059, CVE-2003-0107, CVE-2004-0797, …).
| 2026-09-03: CVE-2026-85091 (high): zlib versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vulnerability in the gz_vacate() function when processing non-blocking gzwrite() operations w |
| 2026-08-24: CVE-2026-76844 (high): zlib 1.2.11 through 1.3.2 contains a heap buffer overflow: after an underlying write() fails, gz_write() returns without resetting strm.next_in, leaving it poin |
| 2026-02-18: CVE-2026-27171 (low): zlib before 1.3.2 allows CPU consumption via crc32_combine64 and crc32_combine_gen64 because x2nmodp can do right shifts within a loop that has no termination c |
| 2026-01-07: CVE-2026-22184 (moderate): zlib versions up to and including 1.3.1.2 include a global buffer overflow in the untgz utility located under contrib/untgz. The vulnerability is limited to the |
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 madler/zlib: 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.