Overview
Express.js security hardening - cookies, CORS, CSRF, rate limiting, and Helmet
Live from GitHub
This content is fetched directly from README.md on GitHub and cached for 1 hour.
AI-Optimized Security
Every rule includes CWE, OWASP, and CVSS metadata for AI assistants to provide precise, context-aware fixes.
Rules (10)
Browse all Express.js security rules with CWE/OWASP mapping
Changelog
View version history and updates
Comprehensive security rules for Express.js applications, mapping to OWASP Top 10.
⭐ If this plugin caught a real bug for you, star the repo — it's the signal that keeps these rules maintained.
Description
This plugin provides Comprehensive security rules for Express.js applications, mapping to OWASP Top 10.
Philosophy
Interlace fosters strength through integration. Instead of stacking isolated rules, we interlace security directly into your workflow to create a resilient fabric of code. We believe tools should guide rather than gatekeep, providing educational feedback that strengthens the developer with every interaction.
Getting Started
- To check out the guide, visit eslint.interlace.tools. 📚
- 要查看中文 指南, 请访问 eslint.interlace.tools. 📚
- 가이드 문서는 eslint.interlace.tools에서 확인하실 수 있습니다. 📚
- ガイドは eslint.interlace.toolsでご確認ください。 📚
- Para ver la guía, visita eslint.interlace.tools. 📚
- للاطلاع على الدليل، قم بزيارة eslint.interlace.tools. 📚
npm install eslint-plugin-express-security --save-dev⚙️ Configuration Presets
| Preset | Description |
|---|---|
recommended | Balanced security for Express projects (critical as error, others warn) |
strict | Maximum security enforcement (all rules as errors) |
api | HTTP/API security rules only (CORS, CSRF, cookies, rate limiting) |
graphql | GraphQL-specific security rules only |
📚 Supported Libraries
| Library | npm | Downloads | Detection |
|---|---|---|---|
express |  |  | Misconfig, DoS |
helmet |  |  | Missing Security Headers |
cors |  |  | Permissive CORS |
csurf |  |  | Missing CSRF Protection |
📦 Compatibility
| Package | Version |
|---|---|
| ESLint | ^8.0.0 || ^9.0.0 || ^10.0.0 |
| Node.js | >=18.0.0 |
See the ESLint Version Support Policy — current ecosystem share data, the 20% gate, and the forward-looking exception that covers v10.
Rules
Legend
| Icon | Description |
|---|---|
| 💼 | Recommended: Included in the recommended preset. |
| ⚠️ | Warns: Set to warn in recommended preset. |
| 🔧 | Auto-fixable: Automatically fixable by the --fix CLI option. |
| 💡 | Suggestions: Providing code suggestions in IDE. |
| 🚫 | Deprecated: This rule is deprecated. |
| 🟢 | Type-unaware: AST-only, runs in oxlint JS-plugin tier. |
| 🟡 | Type-aware (refining): pure-AST primary path; types refine precision. |
| 🟠 | Type-aware (graceful): requires TS program; silent without it. |
| Rule | CWE | OWASP | CVSS | Description | 🧠 | 💼 | ⚠️ | 🔧 | 💡 | 🚫 |
|---|---|---|---|---|---|---|---|---|---|---|
| no-client-controlled-authorization | CWE-863 | A01:2021 | This rule detects access decisions taken on request-supplied role, permission or identity values — the chec… | 🟢 | ||||||
| no-cors-credentials-wildcard | CWE-942 | The rule provides LLM-optimized error messages (Compact 2-line format) with actionable security guidance: | 🟢 | |||||||
| no-disabled-helmet-protections | CWE-693 | A05:2021 | This rule detects helmet options that switch a shipped security-header default off, leaving a mounted helme… | 🟢 | 💼 | |||||
| no-error-details-in-response | CWE-209 | A04:2021 | Disallow sending caught error objects, stack traces, or spreads of them in HTTP responses. | 🟢 | ||||||
| no-exposed-debug-endpoints | CWE-489 | A05:2021 | Identifies potential debug, administration, or testing endpoints that are often left exposed in production… | 🟢 | ||||||
| no-express-unsafe-regex-route | CWE-1333 | This rule detects Regular Expression Denial of Service (ReDoS) vulnerabilities in Express route patterns | 🟢 | |||||||
| no-graphql-introspection-production | CWE-200 | This rule detects GraphQL servers with introspection enabled in production | 🟢 | |||||||
| no-host-header-in-links | CWE-640 | A07:2021 | Disallow building absolute URLs (password-reset and verification links) from the Host or X-Forwarded-Host r… | 🟢 | ||||||
| no-idor-resource-access | CWE-639 | A01:2021 | This rule detects a resource fetched by an identifier taken straight from the request inside a handler that… | 🟢 | ||||||
| no-insecure-cookie-options | CWE-614 | The rule provides LLM-optimized error messages (Compact 2-line format) with actionable security guidance: | 🟢 | 💼 | ||||||
| no-permissive-cors | CWE-942 | Detects overly permissive CORS configurations in Express.js applications | 🟢 | 💼 | ||||||
| no-permissive-trust-proxy | CWE-348 | A05:2021 | This rule detects unconditional 'trust proxy' settings, which make req.ip whatever the caller says it is an… | 🟢 | 💼 | |||||
| no-sensitive-data-in-query | CWE-598 | A04:2021 | Disallow reading sensitive-named parameters (password, token, secret, apiKey, ...) from req.query. | 🟢 | ||||||
| no-static-root-exposure | CWE-548 | A05:2021 | Disallow express.static() roots that expose the application directory and any serve-index usage | 🟢 | ||||||
| no-unsafe-csp-directives | CWE-79 | A03:2021 | This rule detects Content-Security-Policy directives that hand back the protection the header exists to pro… | 🟢 | 💼 | |||||
| no-user-controlled-render-locals | CWE-73 | A03:2021 | Disallow res.render() with locals or view names sourced wholesale from req.body / req.query / req.params | 🟢 | ||||||
| require-case-insensitive-path-guard | CWE-178 | A01:2021 | This rule detects path-based authorization guards that compare req.path case-sensitively, which case-insens… | 🟢 | ||||||
| require-csrf-protection | CWE-352 | The rule provides LLM-optimized error messages (Compact 2-line format) with actionable security guidance: | 🟢 | 💼 | ||||||
| require-express-body-parser-limits | CWE-400 | The rule provides LLM-optimized error messages (Compact 2-line format) with actionable security guidance: | 🟢 | |||||||
| require-helmet | CWE-693 | This rule detects Express.js applications that are missing the helmet middleware | 🟢 | 💼 | ||||||
| require-query-type-guard | CWE-843 | A03:2021 | This rule detects string methods called on req.query values without a type guard — Express query values can… | 🟢 | ||||||
| require-rate-limiting | CWE-770 | This rule detects Express.js applications missing rate limiting middleware | 🟢 | 💼 | ||||||
| require-route-authentication | CWE-306 | A07:2021 | This rule detects routes that expose a critical function — credentials, accounts, payments, configuration —… | 🟢 | ||||||
| require-strict-transport-security | CWE-319 | A02:2021 | This rule detects HSTS configurations that leave a downgrade window open — the header disabled, a max-age b… | 🟢 | 💼 |
🔗 Related ESLint Plugins
Part of the Interlace ESLint Ecosystem — AI-native security plugins with LLM-optimized error messages:
| Plugin | Downloads | Description |
|---|---|---|
eslint-plugin-secure-coding |  | General security rules & OWASP guidelines. |
eslint-plugin-pg |  | PostgreSQL security & best practices. |
eslint-plugin-node-security |  | Node.js core-module security (fs, child_process, vm, crypto, Buffer). |
eslint-plugin-jwt |  | JWT security & best practices. |
eslint-plugin-browser-security |  | Browser-specific security & XSS prevention. |
eslint-plugin-express-security |  | Express.js security hardening rules. |
eslint-plugin-lambda-security |  | AWS Lambda security best practices. |
eslint-plugin-nestjs-security |  | NestJS security rules & patterns. |
eslint-plugin-mongodb-security |  | MongoDB security best practices. |
eslint-plugin-vercel-ai-security |  | Vercel AI SDK security hardening. |
eslint-plugin-import-next |  | Next-gen import sorting & architecture. |
⭐ Support & follow
If this plugin caught a real bug for you, star the repo — stars are the signal that keeps the Interlace ESLint ecosystem maintained — and follow the writeups on Dev.to for the benchmarks and security research behind these rules.
📄 License
MIT © Ofri Peretz
View README.md on GitHub →
Building secure JavaScript with Interlace? Star the repo to get new rules and CWE coverage as we ship them — or follow the AI-code-security benchmarks behind them.