JSPM

Security validation for JSON Web Tokens (JWT) implementation (signing, verification).

Description

Secure your JWT implementation with precision. This plugin enforces critical security best practices, including algorithm whitelisting, expiration validation, and protection against common attacks like algorithm confusion and 'none' algorithm bypasses. Designed for modern stacks, it provides AI-optimized error messages that guide developers to the correct fix instantly, ensuring your authentication layer remains robust against evolving threats.

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-jwt --save-dev

💡 What You Get

• 13 Security Rules - Algorithm attacks, replay prevention, claim validation
• 6 JWT Libraries - jsonwebtoken, jose, express-jwt, @nestjs/jwt, jwks-rsa, jwt-decode
• 2025 Research - "Back to the Future" replay attack prevention (LightSEC 2025)
• AI-Optimized - Structured messages for GitHub Copilot, Cursor, Claude assistance
• CWE References - Every rule maps to Common Weakness Enumeration

⚙️ Configuration Presets

📚 Supported Libraries

Library	npm	Downloads	Detection
jsonwebtoken			Signing, Verification, Decoding
jose			Verification (Fix Suggestion)
jwt-decode			Unsafe Decoding

🤖 AI-Optimized Messages

Every rule uses formatLLMMessage for structured output:

🔒 CWE-347 OWASP:A02-Crypto CVSS:9.8 | Using alg:"none" bypasses signature verification
   Fix: Remove "none" and use RS256, ES256, or other secure algorithms
   https://nvd.nist.gov/vuln/detail/CVE-2022-23540

By providing this structured context (CWE, OWASP, Fix), we enable AI tools to reason about the security flaw rather than hallucinating. This allows Copilot/Cursor to suggest the exact correct fix immediately.

By structuring errors with specific CWE codes, OWASP categories, and direct fix suggestions, this format allows AI coding assistants to autonomously identify, explain, and resolve security vulnerabilities with high confidence.

Rules

Legend

🔗 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-crypto		NodeJS Cryptography security rules.
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.

📄 License

MIT © Ofri Peretz