npm package
nanoid 3.3.18: no known vulnerabilities
nanoid 3.3.18 has no known vulnerabilities in OSV.dev.
npm (opens in a new tab) describes it as “A tiny (117 bytes), secure URL-friendly unique string ID generator”
- Known vulnerabilities
- 0
- None in OSV.dev
- Released
- Aug 7, 2026
- Latest is 6.0.2
- Downloads last week
- 55.5M
- 20% of nanoid downloads
- Licence
- MIT
- Dependencies
- None
- Resolved by deps.dev
Newer releases
3.3.18 has nothing to fix today. Newer releases, for when you upgrade:
Newest 3.x release. Released Oct 5, 2026.
No known vulnerabilitiesLatest release. Released Oct 5, 2026.
No known vulnerabilities
Hand the fix to your coding agent
One task with the upgrade, the file to change and why. Paste it into Claude Code, Cursor or Codex.
Findings
- WarningOutdated
nanoid 3.3.18 is 3 major versions behind
Latest release is 6.0.2.
Who is still on a vulnerable nanoid
42% of last week’s 273.5M nanoid downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Is nanoid the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly nanoid 3.3.18, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.