Check a mark
A Borehole code resolves to the analysis we actually ran. Type the code printed on a report and this page re-renders the authoritative version — not a claim about it.
Twelve characters. Case and dashes do not matter.
Verified
This code matches a Borehole analysis of nlohmann/json, and the record is unchanged since the mark was issued.
- Repository
- nlohmann/json
- Commit
- 633de8e44bbbc29383d72f8c920343ea5d1eaa21
- Surveyed
- 2026-10-03
- Mark issued
- 2026-10-03
- Assessor
- borehole 0.7.11
- Checks run
- 104
- Ran in
- cloud-run — not attested
This commit has been surveyed again since this mark was issued. The mark above is still valid — it attests to the survey it was issued for, and always will. But a newer reading of the same commit exists, made by borehole 0.7.13 on 2026-10-04, finding 3 things against this one's 3. Read the newer one.
This mark covers 104 checks. Borehole now runs 106. A mark attests to the survey that was run, not to the checks written since it was issued. If the newer checks matter to you, ask for a fresh repo survey at this commit.
What the analysis recorded
| Dimension | Band | Findings |
|---|---|---|
| Architecture & Codebase — including AI provenance | strong | 1 |
| Engineering Process & SDLC Maturity | strong | 0 |
| Organization & Key-Person Risk | not assessable | 0 |
| Product & Engineering Maturity | adequate | 2 |
| Security & Reliability Posture | not assessable | 0 |
| Observability & Operations | not assessable | 0 |
| Fit with the Acquirer | not assessable | 0 |