Summary
Togoder Security scanned the npm package uncrypto@0.1.3 on Oct 4, 2026. An AI review of 4 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/crypto.node.cjs | safe | The file provides a minimal, transparent wrapper around Node's built-in crypto module with no obfuscation, external network calls, environment harvesting, dynamic code execution, or suspicious import-time behavior. |
| dist/crypto.node.mjs | safe | No malicious patterns detected |
| dist/crypto.web.cjs | safe | No malicious patterns detected; the code is a simple, transparent wrapper around the standard Web Crypto API. |
| dist/crypto.web.mjs | safe | No malicious patterns detected |
Scanned versions of uncrypto
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 0.1.3 | No issues | 4 | Oct 4, 2026 |
Frequently asked questions
Is uncrypto safe to use?
Our AI source review of uncrypto@0.1.3 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does uncrypto contain malware?
No malware was identified in uncrypto@0.1.3 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 uncrypto checked?
Togoder Security downloaded the published npm package and had an AI model read its 4 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 uncrypto 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 uncrypto@0.1.3, cost nothing.