Summary
Togoder Security scanned the npm package get-nonce@1.0.1 on Oct 6, 2026. An AI review of 2 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/es2015/index.js | safe | No malicious patterns detected; the code only manages a nonce value for webpack's Content Security Policy integration. |
| dist/es5/index.js | safe | No malicious patterns detected |
Frequently asked questions
Is get-nonce safe to use?
Our AI source review of get-nonce@1.0.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does get-nonce contain malware?
No malware was identified in get-nonce@1.0.1 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 get-nonce checked?
Togoder Security downloaded the published npm package and had an AI model read its 2 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 get-nonce 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 get-nonce@1.0.1, cost nothing.