Summary
Togoder Security scanned the npm package eslint-plugin-security@4.2.0 on Oct 6, 2026. An AI review of 22 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 |
|---|---|---|
| .eslint-doc-generatorrc.js | safe | Cleared by Jev triage; no further analysis needed |
| eslint.config.js | safe | Cleared by Jev triage; no further analysis needed |
| index.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-bidi-characters.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-buffer-noassert.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-child-process.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-disable-mustache-escape.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-eval-with-expression.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-invisible-characters.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-new-buffer.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-no-csrf-before-method-override.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-non-literal-fs-filename.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-non-literal-regexp.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-non-literal-require.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-object-injection.js | safe | No malicious patterns detected; this is a standard ESLint security rule that statically analyzes JavaScript code for computed member expressions that could be object injection sinks. |
| rules/detect-possible-timing-attacks.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-pseudoRandomBytes.js | safe | Cleared by Jev triage; no further analysis needed |
| rules/detect-unsafe-regex.js | safe | Cleared by Jev triage; no further analysis needed |
| types/index.test-d.ts | safe | Cleared by Jev triage; no further analysis needed |
| utils/find-variable.js | safe | Cleared by Jev triage; no further analysis needed |
| utils/import-utils.js | safe | Cleared by Jev triage; no further analysis needed |
| utils/is-static-expression.js | safe | Cleared by Jev triage; no further analysis needed |
Scanned versions of eslint-plugin-security
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 4.2.0 | No issues | 22 | Oct 6, 2026 |
Frequently asked questions
Is eslint-plugin-security safe to use?
Our AI source review of eslint-plugin-security@4.2.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does eslint-plugin-security contain malware?
No malware was identified in eslint-plugin-security@4.2.0 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-plugin-security checked?
Togoder Security downloaded the published npm package and had an AI model read its 22 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-plugin-security 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-plugin-security@4.2.0, cost nothing.