Read 2026-10-04
humanizr/humanizer: technical due diligence, read from its repository
What Borehole read in humanizr/humanizer's code and history at ffc2b77: 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 | strong |
| Security & Reliability Posture | adequate |
| 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
strongsrc/Humanizer/FluentDate/On.Days.cs is 2,345 lines, 57× this codebase's median file
adequateThe median source file here is 41 lines. 12 files exceed 1,000 lines, the largest being 2,345. 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/Humanizer/FluentDate/On.Days.cs:1 — 2,345 lines (57× median) |
src/Humanizer/FluentDate/OnDate.Days.cs:1 — 2,336 lines (56× median) |
src/Humanizer/Bytes/ByteSize.cs:1 — 1,841 lines (44× median) |
src/Humanizer/Localisation/WordsToNumber/TokenMapWordsToNumberConverter.cs:1 — 1,719 lines (41× median) |
src/Humanizer.SourceGenerators/Common/LocaleYamlCatalog.cs:1 — 1,696 lines (41× median) |
Engineering Process & SDLC Maturity
adequate7% of recent commits change more than 2,000 lines
adequate30 of 404 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.
| 30 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v3.0.10, is not on the branch this survey read; the newest release on it is v2.14.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v3.0.10 |
Security & Reliability Posture
adequate13 locked dependencies have published vulnerabilities, 20 high or critical in what ships
adequate13 of 1,238 locked dependencies match 36 published advisories in OSV, 20 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.
website/pnpm-lock.yaml — brace-expansion 1.1.18: GHSA-6j4f-fj2g-mc7p (high), fixed in 1.1.19 |
website/pnpm-lock.yaml — braces 3.0.3: GHSA-vfj7-8cjw-p6xm (high) |
website/pnpm-lock.yaml — fast-uri 3.1.4: GHSA-5jgf-p345-68v8 (high), fixed in 3.1.6 |
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 humanizr/humanizer: 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.