Summary
Togoder Security scanned the npm package @eslint/config-array@0.23.5 on Oct 6, 2026. An AI review of 7 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/cjs/index.cjs | safe | No malicious patterns detected in the reviewed JavaScript file; it is a legitimate ESLint config-array utility with no network, filesystem, process execution, or obfuscation concerns. |
| dist/cjs/std__path/posix.cjs | safe | No malicious patterns detected; the file is a legitimate POSIX path manipulation module from the Deno standard library with no network, filesystem, process, or obfuscated code. |
| dist/cjs/std__path/windows.cjs | safe | No malicious patterns detected; this is a legitimate Deno standard library path module port with only standard path manipulation logic and no network, process, filesystem, or credential access. |
| dist/esm/index.js | safe | No malicious patterns detected; the code is a legitimate ESLint config array implementation with no exfiltration, credential harvesting, obfuscation, or other red flags. |
| dist/esm/std__path/posix.js | safe | No malicious patterns detected; this is a legitimate Deno std path utility module with only standard path manipulation functions. |
| dist/esm/std__path/windows.js | safe | This is a legitimate, unmodified copy of the Deno standard library's Windows path utilities with no malicious patterns detected. |
| dist/esm/types.ts | safe | Cleared by Jev triage; no further analysis needed |
Frequently asked questions
Is @eslint/config-array safe to use?
Our AI source review of @eslint/config-array@0.23.5 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @eslint/config-array contain malware?
No malware was identified in @eslint/config-array@0.23.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 @eslint/config-array checked?
Togoder Security downloaded the published npm package and had an AI model read its 7 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 @eslint/config-array 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 @eslint/config-array@0.23.5, cost nothing.