# @nodelib/fs.scandir@2.1.5 security report (npm)

- Verdict: **No issues** (risk level: safe)
- Scanned: 2026-10-06T14:11:19.000Z
- Files reviewed: 10
- Findings: no findings
- Report: https://security.togoder.click/npm/@nodelib/fs.scandir
- Source: Togoder Security (https://security.togoder.click), AI source-code review

## 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.

## Files reviewed

- `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

AI analysis is guidance, not a guarantee. Methodology: https://security.togoder.click/methodology