Overview

  

  

⭐ 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 Maintainability rules — complexity ceilings, dead code, and readability guardrails.

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.

Why these rules are quiet

Noise creates apathy, and apathy is not a security posture. A linter that reports a thousand things a week gets switched off in a month, and the real finding goes with it. So every rule here is built to be worth reading: we would rather miss a finding than spend your attention on one that was never real.

That is a trade, and it is made deliberately. It costs recall, and we measure what it costs rather than assuming it is free.

How the rules decide

Evidence, not names. A rule fires on what the code does, resolved through the AST and ESLint's own scope analysis — not on an identifier that happens to contain query, a method called setItem, or a file whose path contains key. Every one of those was a real false positive in this ecosystem, found by reading our own output on open-source projects and fixed with a test that fails on the unfixed rule.

Where a rule has known false-positive shapes, its page carries a Not a finding section: what it deliberately stays quiet on, and what to check first when it fires and you disagree.

What you get

The rules below. Security rules carry a CWE mapping and, where one is assigned, a CVSS score; every rule carries a fix on its message — in prose for a human and as structured JSON for an agent. Install it, enable recommended, and read the findings. If one of them is wrong, open an issue — a false positive is a bug here, not a tuning exercise for you.

How that is measured, on which projects, and where it falls short: benchmark methodology and results.

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

⚙️ Configuration Presets

📦 Compatibility

See the ESLint Version Support Policy — current ecosystem share data, the 20% gate, and the forward-looking exception that covers v10.

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-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