Summary
Togoder Security scanned the npm package uuid@8.3.2 on Oct 4, 2026. An AI review of 50 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 |
|---|---|---|
| dist/esm-browser/index.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-browser/md5.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-browser/nil.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-browser/parse.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-browser/regex.js | safe | No malicious patterns detected |
| dist/esm-browser/rng.js | safe | No malicious patterns detected; the code only uses the browser's crypto.getRandomValues API to generate random bytes for UUID generation with proper polyfill fallback. |
| dist/esm-browser/sha1.js | safe | This is a standard, self-contained SHA-1 implementation with no network calls, filesystem access, command execution, obfuscation, or other malicious patterns. |
| dist/esm-browser/stringify.js | safe | No malicious patterns detected |
| dist/esm-browser/v1.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-browser/v3.js | safe | No malicious patterns detected |
| dist/esm-browser/v35.js | safe | No malicious patterns detected; the code implements RFC 4122 UUID v3/v5 generation without any exfiltration, obfuscation, process execution, or filesystem access. |
| dist/esm-browser/v4.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-browser/v5.js | safe | No malicious patterns detected |
| dist/esm-browser/validate.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-browser/version.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/index.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/md5.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/nil.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/parse.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/regex.js | safe | No malicious patterns detected |
| dist/esm-node/rng.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/sha1.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/stringify.js | safe | No malicious patterns detected; the code is a standard UUID stringification utility from the uuid npm package. |
| dist/esm-node/v1.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/v3.js | safe | Cleared by Jev triage; no further analysis needed |
Show 25 more files
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/esm-node/v35.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/v4.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/v5.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/validate.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/esm-node/version.js | safe | Cleared by Jev triage; no further analysis needed |
| dist/index.js | safe | No malicious patterns detected |
| dist/md5-browser.js | safe | No malicious patterns detected |
| dist/md5.js | safe | No malicious patterns detected |
| dist/nil.js | safe | No malicious patterns detected |
| dist/parse.js | safe | No malicious patterns detected |
| dist/regex.js | safe | No malicious patterns detected |
| dist/rng-browser.js | safe | No malicious patterns detected; the code is a standard UUID randomness source that uses the browser crypto API with proper validation and no external communication or obfuscation. |
| dist/rng.js | safe | No malicious patterns detected; the code is a standard cryptographically secure random number generator using crypto.randomFillSync. |
| dist/sha1-browser.js | safe | No malicious patterns detected; the file is a standard, self-contained SHA1 hash implementation with no network, filesystem, process, or dynamic code execution behavior. |
| dist/sha1.js | safe | No malicious patterns detected |
| dist/stringify.js | safe | No malicious patterns detected; the code is a standard UUID stringification utility with input validation. |
| dist/uuid-bin.js | safe | No malicious patterns detected |
| dist/v1.js | safe | This is a legitimate UUID v1 generation module with no malicious patterns, network calls, or process execution. |
| dist/v3.js | safe | This file is a standard UUID v3 implementation that imports local modules and exports a function without any suspicious behavior. |
| dist/v35.js | safe | No malicious patterns detected |
| dist/v4.js | safe | This is a standard UUID v4 generation module with no malicious patterns detected. |
| dist/v5.js | safe | No malicious patterns detected; this is a standard UUID v5 module entry point. |
| dist/validate.js | safe | No malicious patterns detected |
| dist/version.js | safe | No malicious patterns detected |
| wrapper.mjs | safe | Cleared by Jev triage; no further analysis needed |
Affected version ranges
None of the 3 scanned versions of uuid are flagged high or critical. The latest scanned version, 14.0.2, is not scanned. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 13.0.2 – 14.0.2 | Not scanned | 3 | >=13.0.2 <=14.0.2 | |
| 11.1.1 | No issues | 1 | 11.1.1 | |
| 11.0.3 – 11.1.0 | Not scanned | 2 | >=11.0.3 <=11.1.0 | |
| 8.3.2 – 9.0.1 | No issues | 2 | >=8.3.2 <=9.0.1 | |
| 3.2.1 – 7.0.3 | Not scanned | 3 | >=3.2.1 <=7.0.3 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of uuid
Frequently asked questions
Is uuid safe to use?
Our AI source review of uuid@8.3.2 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does uuid contain malware?
No malware was identified in uuid@8.3.2 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was uuid checked?
Togoder Security downloaded the published npm package and had an AI model read its 50 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 uuid 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 uuid@8.3.2, cost nothing.