eslint-plugin-reliability
ESLint rules for code reliability and error prevention
Reliable Code
Prevent runtime errors and ensure code reliability with defensive programming patterns.
Install
npm install -D eslint-plugin-reliabilityLive from GitHub
This content is fetched directly from README.md on GitHub and cached for 1 hour.
⭐ 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 Reliability rules for defensive programming, error handling, and async correctness.
- Why — a linter nobody reads protects nothing. We would rather miss a finding than spend your attention on one that was never real.
- How — evidence, not names. A rule fires on what the code does, resolved through the AST and ESLint's own scope analysis.
- What — every finding carries its fix, in prose for a human and as structured JSON for an agent. Security rules add a CWE mapping and, where assigned, a CVSS score.
That trade costs recall, and we measure it: methodology · results · a false positive is a bug.
Getting Started
- To check out the guide, visit eslint.interlace.tools. 📚
npm install eslint-plugin-reliability --save-dev⚙️ Configuration Presets
| Preset | Description |
|---|---|
recommended | Balanced reliability checks for most projects |
🏢 Usage Example
// eslint.config.js
import reliability from 'eslint-plugin-reliability';
export default [reliability.configs.recommended];Why These Rules?
no-silent-errors
Empty catch blocks hide errors, making debugging impossible.
// ❌ Bad: Silent error swallowing
try {
await processPayment(order);
} catch (e) {
// Error is silently ignored!
}
// ✅ Good: Handle or log the error
try {
await processPayment(order);
} catch (e) {
logger.error('Payment processing failed', { orderId: order.id, error: e });
throw new PaymentError('Payment failed', { cause: e });
}no-missing-null-checks
Catches potential null or undefined dereferences.
// ❌ Bad: Potential runtime error
function greet(user: User | null) {
return `Hello, ${user.name}`; // TypeError if user is null!
}
// ✅ Good: Null-safe access
function greet(user: User | null) {
return user ? `Hello, ${user.name}` : 'Hello, guest';
}require-network-timeout
Network requests without timeouts can hang indefinitely.
// ❌ Bad: No timeout, can hang forever
const response = await fetch('/api/data');
// ✅ Good: Request with timeout
const controller = new AbortController();
const timeoutId = setTimeout(() => controller.abort(), 5000);
const response = await fetch('/api/data', {
signal: controller.signal,
});
clearTimeout(timeoutId);no-await-in-loop
Sequential awaits in loops cause N+1 performance issues.
// ❌ Bad: Sequential requests (slow)
for (const id of userIds) {
const user = await fetchUser(id); // N sequential requests
results.push(user);
}
// ✅ Good: Parallel requests (fast)
const results = await Promise.all(userIds.map((id) => fetchUser(id)));📦 Compatibility
| Package | Version |
|---|---|
| ESLint | ^8.40.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 | 🧠 | 💼 | ⚠️ | 🔧 | 💡 | 🚫 |
|---|---|---|---|---|---|---|---|---|---|---|
| error-message | Enforce providing a message when creating built-in Error objects for better debugging. This rule is part of… | 🟢 | 💡 | |||||||
| no-await-in-loop | Disallow await inside loops without considering concurrency implications | 🟢 | 💡 | |||||||
| no-jsdoc-terminator-in-example | Detect */ sequences inside JSDoc @example blocks that prematurely close the JSDoc comment. | 🟢 | 💡 | |||||||
| no-missing-error-context | ESLint Rule: no-missing-error-context with LLM-optimized suggestions and auto-fix capabilities. | 🟢 | 💡 | |||||||
| no-missing-null-checks | CWE-476 | ESLint Rule: no-missing-null-checks with LLM-optimized suggestions and auto-fix capabilities. | 🟢 | ⚠️ | 💡 | |||||
| no-silent-errors | ESLint Rule: no-silent-errors with LLM-optimized suggestions and auto-fix capabilities. | 🟢 | 💼 | 💡 | ||||||
| no-unhandled-promise | CWE-1024 | Disallow unhandled Promise rejections with LLM-optimized suggestions for proper async error handling. This… | 🟢 | 💡 | ||||||
| no-unsafe-type-narrowing | ESLint Rule: no-unsafe-type-narrowing with LLM-optimized suggestions and auto-fix capabilities. | 🟢 | 💡 | |||||||
| require-network-timeout | Require timeout configuration for network requests. This rule is part of eslint-plugin-reliability and prov… | 🟢 | 💼 | 💡 |
🔗 Related ESLint Plugins
Part of the Interlace ESLint ecosystem — AI-native rules with LLM-optimized error messages:
Security
Code quality
| Plugin | Downloads | Description |
|---|---|---|
eslint-plugin-conventions | Team-specific habits and styles. | |
eslint-plugin-import-next | Fast cycle + import-graph analysis. | |
eslint-plugin-maintainability | Cognitive load and clean-code patterns. | |
eslint-plugin-modernization | ESNext migration + syntax evolution. | |
eslint-plugin-modularity | Structural integrity and DDD patterns. | |
eslint-plugin-operability | Production readiness and resource health. | |
eslint-plugin-react-a11y | React accessibility / WCAG. | |
eslint-plugin-react-features | React best practices and optimization. |
⭐ 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.