Summary
Togoder Security scanned the npm package nanoid@3.3.18 on Oct 6, 2026. An AI review of 15 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| async/index.browser.cjs | safe | No malicious patterns detected |
| async/index.browser.js | safe | Cleared by Jev triage; no further analysis needed |
| async/index.cjs | safe | No malicious patterns detected; the code is a standard cryptographic random ID generator with no suspicious behavior. |
| async/index.js | safe | Cleared by Jev triage; no further analysis needed |
| async/index.native.js | safe | No malicious patterns detected; the code is a standard nanoid implementation using expo-random for cryptographically secure random bytes. |
| bin/nanoid.cjs | safe | No malicious patterns detected; this is a standard CLI wrapper for the nanoid library that processes arguments and prints generated IDs. |
| index.browser.cjs | safe | Cleared by Jev triage; no further analysis needed |
| index.browser.js | safe | Cleared by Jev triage; no further analysis needed |
| index.cjs | safe | No malicious patterns detected |
| index.js | safe | No malicious patterns detected; the code is a legitimate, well-known ID generation library (nanoid) that uses secure random bytes and does not perform any external communication, credential harvesting, or dynamic code execution. |
| nanoid.js | safe | No malicious patterns detected |
| non-secure/index.cjs | safe | Cleared by Jev triage; no further analysis needed |
| non-secure/index.js | safe | Cleared by Jev triage; no further analysis needed |
| url-alphabet/index.cjs | safe | Cleared by Jev triage; no further analysis needed |
| url-alphabet/index.js | safe | Cleared by Jev triage; no further analysis needed |
Affected version ranges
None of the 2 scanned versions of nanoid are flagged high or critical. The latest scanned version, 5.1.16, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 3.3.18 – 5.1.16 | No issues | 2 | >=3.3.18 <=5.1.16 | |
| 2.1.11 – 3.3.15 | Not scanned | 3 | >=2.1.11 <=3.3.15 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of nanoid
Frequently asked questions
Is nanoid safe to use?
Our AI source review of nanoid@3.3.18 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does nanoid contain malware?
No malware was identified in nanoid@3.3.18 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was nanoid checked?
Togoder Security downloaded the published npm package and had an AI model read its 15 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan nanoid together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in nanoid@3.3.18, cost nothing.