Read 2026-11-07
ai/nanoid: technical due diligence, read from its repository
What Borehole read in ai/nanoid's code and history at 35ea7d0: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongAlmost 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 46 tracked files |
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 173 absorb 49% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
package.json — 608 commits touched it |
README.md — 357 commits touched it |
README.ru.md — 98 commits touched it |
README.zh-CN.md — 79 commits touched it |
index.js — 70 commits touched it |
Effort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.77 to 1.13 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.77, second half 1.13 (split 2022-03-11) |
Security & Reliability Posture
strong4 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-08-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. None of them affects the surveyed version.
| 2026-08-03: GHSA-xwg4-73v4-xw9w (high), fixed in 3.3.12: nanoid: Integer Overflow or Wraparound |
| 2026-07-29: GHSA-28wg-ghj8-5hjv (high), fixed in 3.3.16: nanoid: non-secure generators can loop indefinitely with negative size |
| 2026-07-29: GHSA-2v37-7h3g-55p8 (high), fixed in 3.3.18: nanoid: custom generators can loop indefinitely when size is zero |
| 2024-12-09: GHSA-mwcw-c2x4-8c55 (moderate), fixed in 3.3.8: Predictable results in nanoid generation when given non-integer values |
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 ai/nanoid: 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.