Summary
Togoder Security scanned the npm package @nodelib/fs.scandir@2.1.5 on Oct 6, 2026. An AI review of 10 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 |
|---|---|---|
| out/adapters/fs.js | safe | The file is a simple, transparent file system adapter that wraps core Node.js fs methods without any malicious patterns. |
| out/constants.js | safe | No malicious patterns detected |
| out/index.js | safe | No malicious patterns detected |
| out/providers/async.js | safe | No malicious patterns detected |
| out/providers/common.js | safe | No malicious patterns detected |
| out/providers/sync.js | safe | The code is a legitimate utility for synchronously reading directory entries with support for symbolic links and file stats, containing no malicious patterns. |
| out/settings.js | safe | No malicious patterns detected; the file defines a Settings class for configuring filesystem stat operations with no network, process execution, credential harvesting, or dynamic code evaluation. |
| out/types/index.js | safe | No malicious patterns detected |
| out/utils/fs.js | safe | No malicious patterns detected; the code only wraps Node.js fs.Stats methods into a Dirent-like object with no I/O, network, or dynamic execution. |
| out/utils/index.js | safe | No malicious patterns detected |
Frequently asked questions
Is @nodelib/fs.scandir safe to use?
Our AI source review of @nodelib/fs.scandir@2.1.5 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @nodelib/fs.scandir contain malware?
No malware was identified in @nodelib/fs.scandir@2.1.5 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 @nodelib/fs.scandir checked?
Togoder Security downloaded the published npm package and had an AI model read its 10 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 @nodelib/fs.scandir 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 @nodelib/fs.scandir@2.1.5, cost nothing.