Borehole · Project · free tier
nlohmann/json
Free reading: not for reliance
633de8e · 5,165 commits · 1,275 files
Read 2026-10-04

nlohmann/json: technical due diligence, read from its repository

What Borehole read in nlohmann/json's code and history at 633de8e: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Posturenot assessable
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • No release for 17 months while development continues
  • Releases are cut from another branch than the one surveyed
  • README.md:20: names OpenSSF

Architecture & Codebase — including AI provenance

strong
01.6

include/nlohmann/json.hpp is 6,628 lines, 194× this codebase's median file

adequate

The median source file here is 34 lines. 8 files exceed 1,000 lines, the largest being 6,628. 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.

Evidence
include/nlohmann/json.hpp:1 — 6,628 lines (194× median)
include/nlohmann/detail/input/binary_reader.hpp:1 — 4,352 lines (128× median)
include/nlohmann/detail/output/binary_writer.hpp:1 — 2,618 lines (77× median)
include/nlohmann/detail/input/lexer.hpp:1 — 2,338 lines (68× median)
include/nlohmann/detail/output/serializer.hpp:1 — 1,672 lines (49× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.61

No release for 17 months while development continues

adequate

The last tag, v3.12.0, was cut 535 days before the survey; the typical gap between releases was 26 days, and 220 commits landed in the last 90 days. Users run the last release, not this code.

Evidence
last tag v3.12.0
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v3.12.0, is not on the branch this survey read; the newest release on it is v3.11.3. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v3.12.0

Security & Reliability Posture

not assessable

Not rated: only 15 of 34 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on nlohmann/json: 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.