Overview
NestJS security rules for guards, validation pipes, throttling, and more
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 (6)
Browse all NestJS security rules with CWE/OWASP mapping
Changelog
View version history and updates
Security rules tailored for NestJS applications (Controllers, Providers, Decorators).
โญ 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 Security rules tailored for NestJS applications (Controllers, Providers, Decorators).
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-nestjs-security --save-devโ๏ธ Configuration Presets
| Preset | Description |
|---|---|
recommended | Enables all security rules with sensible severity levels |
strict | All security rules set to 'error' for maximum protection |
๐ Supported Libraries
| Library | npm | Downloads | Detection |
|---|---|---|---|
@nestjs/common | Decorators, Guards | ||
@nestjs/core | App Config | ||
class-validator | DTO Validation | ||
@nestjs/throttler | Rate Limiting |
โ ๏ธ Global Configuration Handling
Static Analysis Limitation: ESLint analyzes files independently. It cannot detect cross-file configurations like
app.useGlobalGuards()inmain.tswhile lintingusers.controller.ts.
Understanding the Problem
NestJS supports two security configuration approaches:
| Approach | Example | ESLint Can See? |
|---|---|---|
| Per-Controller | @UseGuards(AuthGuard) on class | โ |
| Per-Method | @UseGuards(AuthGuard) on method | โ |
| Global (main.ts) | app.useGlobalGuards(new AuthGuard()) | โ |
| Global (Module) | ThrottlerModule.forRoot({ ttl: 60, limit: 10 }) | โ |
Solution: assumeGlobal* Options
For teams using global configuration, set assumeGlobal*: true to disable per-file checks:
// eslint.config.js
import nestjsSecurity from 'eslint-plugin-nestjs-security';
export default [
{
...nestjsSecurity.configs.recommended,
rules: {
// Tell ESLint: "We have app.useGlobalGuards() in main.ts"
'nestjs-security/require-guards': ['warn', { assumeGlobalGuards: true }],
// Tell ESLint: "We have app.useGlobalPipes(new ValidationPipe()) in main.ts"
'nestjs-security/no-missing-validation-pipe': [
'warn',
{ assumeGlobalPipes: true },
],
// Tell ESLint: "We have ThrottlerModule.forRoot() in app.module.ts"
'nestjs-security/require-throttler': [
'warn',
{ assumeGlobalThrottler: true },
],
},
},
];Alternative: Use Skip Decorators
The rules recognize common "bypass" decorators for intentionally unprotected endpoints:
// These bypass require-guards
@Public() // nestjs-passport pattern
@SkipAuth() // common custom decorator
@AllowAnonymous() // alternative naming
@NoAuth() // alternative naming
// These bypass require-throttler
@SkipThrottle() // @nestjs/throttler built-in๐ฎ Future: Cross-File Global Detection (Planned)
We're planning dedicated rules to verify global configuration exists:
require-global-guardsโ Ensuresmain.tscontainsapp.useGlobalGuards()require-global-validation-pipeโ Ensuresmain.tscontainsapp.useGlobalPipes()require-global-throttlerโ Ensuresapp.module.tsimportsThrottlerModule
This will enable a "trust but verify" approach for teams using global configuration.
๐ฆ 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-exposed-debug-endpoints | CWE-489 | Identifies potential debug, administration, or testing endpoints that are often left exposed in productionโฆ | ๐ข | |||||||
| no-exposed-private-fields | CWE-200 | A01:2021 | This rule detects sensitive fields (like passwords, tokens, secrets) in entity or DTO classes that are notโฆ | ๐ข | ||||||
| no-missing-validation-pipe | CWE-20 | A03:2021 | The rule provides LLM-optimized error messages (Compact 2-line format) with actionable security guidance: | ๐ข | ||||||
| require-class-validator | CWE-20 | A03:2021 | The rule provides LLM-optimized error messages (Compact 2-line format) with actionable security guidance: | ๐ข | ||||||
| require-guards | CWE-284 | A01:2021 | The rule provides LLM-optimized error messages (Compact 2-line format) with actionable security guidance: | ๐ข | ๐ผ | |||||
| require-throttler | CWE-770 | A05:2021 | This rule detects NestJS controllers and route handlers that lack rate limiting, which can make the applicaโฆ | ๐ข |
๐ 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 โ
