A benchmark-style write-up evaluates **@microsoft/eslint-plugin-sdl** against a broader set of Node.js security test cases.

**Reported result**

- Detected 4/40 vulnerable patterns (~10%), but performed well on its focus area (DOM/XSS and code execution prevention).

**Why it matters**

Security plugins can create a false sense of coverage. Backend-heavy JavaScript apps still need checks for SSRF, injection, path traversal, weak crypto, and more.

**Practical takeaway**

Use the SDL ESLint plugin for DOM safety, but pair it with Node-focused rules, dependency scanning, and security review for server-side code.

**Tags:** Web Development, Cyber Security, JavaScript, Node.js