eslint-plugin-reliability

Security-focused ESLint plugin.

Description

This plugin provides Security-focused ESLint plugin.
By using this plugin, you can proactively identify and mitigate security risks across your entire codebase.

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

``bash npm install eslint-plugin-reliability --save-dev`

`⚙️ Configuration Presets`


| Preset        | Description                                   |
| :------------ | :-------------------------------------------- |
|

recommended

 | Balanced reliability checks for most projects |
---
🏢 Usage Example

js
// eslint.config.js
import reliability from 'eslint-plugin-reliability';

export default [reliability.configs.recommended];`

---

`Why These Rules?`


$3
Empty catch blocks hide errors, making debugging impossible.

`ts // ❌ 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 }); }`

`$3`

Catches potential null or undefined dereferences.

`ts // ❌ Bad: Potential runtime error function greet(user: User | null) { returnHello, ${user.name}; // TypeError if user is null! }

// ✅ Good: Null-safe access function greet(user: User | null) { return user ?Hello, ${user.name}: 'Hello, guest'; }`

`$3`

Network requests without timeouts can hang indefinitely.

`ts // ❌ 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);`

`$3`

Sequential awaits in loops cause N+1 performance issues.

`ts // ❌ 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)));`

---

`Rules`

Legend

| Icon | Description | | :---: | :--- | | 💼 | Recommended: Included in the recommended preset. | | ⚠️ | Warns: Set towarn in recommended preset. | | 🔧 | Auto-fixable: Automatically fixable by the--fixCLI option. | | 💡 | Suggestions: Providing code suggestions in IDE. | | 🚫 | Deprecated: This rule is deprecated. |

| Rule | CWE | OWASP | CVSS | Description | 💼 | ⚠️ | 🔧 | 💡 | 🚫 | | :--- | :---: | :---: | :---: | :--- | :---: | :---: | :---: | :---: | :---: | | error-handling | | | | Enforce error handling | | | | | | | reliability | | | | Enforce reliability | | | | | |

`🔗 Related ESLint Plugins`

Part of the Interlace ESLint Ecosystem — AI-native security plugins with LLM-optimized error messages:

📄 License

MIT © Ofri Peretz

Security-focused ESLint plugin.

Description

This plugin provides Security-focused ESLint plugin.
By using this plugin, you can proactively identify and mitigate security risks across your entire codebase.

Philosophy

Getting Started

``bash npm install eslint-plugin-reliability --save-dev`

`⚙️ Configuration Presets`


| Preset        | Description                                   |
| :------------ | :-------------------------------------------- |
|

recommended

 | Balanced reliability checks for most projects |
---
🏢 Usage Example

js
// eslint.config.js
import reliability from 'eslint-plugin-reliability';

export default [reliability.configs.recommended];`

---

`Why These Rules?`


$3
Empty catch blocks hide errors, making debugging impossible.

`ts // ❌ Bad: Silent error swallowing try { await processPayment(order); } catch (e) { // Error is silently ignored! }

`$3`

Catches potential null or undefined dereferences.

`ts // ❌ Bad: Potential runtime error function greet(user: User | null) { returnHello, ${user.name}; // TypeError if user is null! }

// ✅ Good: Null-safe access function greet(user: User | null) { return user ?Hello, ${user.name}: 'Hello, guest'; }`

`$3`

Network requests without timeouts can hang indefinitely.

`ts // ❌ 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);`

`$3`

Sequential awaits in loops cause N+1 performance issues.

`ts // ❌ 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)));`

---

`Rules`

Legend

`🔗 Related ESLint Plugins`

Part of the Interlace ESLint Ecosystem — AI-native security plugins with LLM-optimized error messages: