Summary
Togoder Security scanned the npm package levn@0.4.1 on Oct 6, 2026. An AI review of 3 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 |
|---|---|---|
| lib/cast.js | safe | No malicious patterns detected; the code is a type casting utility with no network, filesystem, process execution, or obfuscation concerns. |
| lib/index.js | safe | No malicious patterns detected |
| lib/parse-string.js | safe | No malicious patterns detected; the code is a benign string parser with no network, filesystem, process execution, or obfuscated behavior. |
Frequently asked questions
Is levn safe to use?
Our AI source review of levn@0.4.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does levn contain malware?
No malware was identified in levn@0.4.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 levn checked?
Togoder Security downloaded the published npm package and had an AI model read its 3 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 levn 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 levn@0.4.1, cost nothing.