eslint-plugin-postgresql-security
PostgreSQL security and best practices for the pg driver
AI-Optimized Security
Every rule includes CWE, OWASP, and CVSS metadata for AI assistants to provide precise, context-aware fixes.
Install
npm install -D eslint-plugin-postgresql-securityRules (13)
Browse all PostgreSQL security rules with CWE/OWASP mapping
Changelog
View version history and updates
Live 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 Security rules for PostgreSQL interaction in Node.js (SQL injection prevention).
Why pg-specific?
A generic SQL injection linter can flag string concatenation wherever it appears, but it cannot know the parameterization convention for each database client. The pg (node-postgres) driver uses $1, $2, … positional placeholders with a second-argument array — a pattern no generic rule encodes. eslint-plugin-postgresql-security knows this contract: it only fires on .query() calls, it stays silent when a second argument (the values array) is present, and it tracks variable taint across assignment statements so that a split-line pattern like const sql = "SELECT..." + id; client.query(sql) is flagged even though the concatenation and the query call are on separate lines. The result is a rule with near-zero false positives on legitimate parameterized queries and reliable detection on the patterns that actually lead to SQL injection.
- 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-postgresql-security --save-dev⚙️ Configuration Presets
| Preset | Description |
|---|---|
recommended | Recommended preset - balanced security for most projects |
strict | Strict preset - all rules as errors |
📚 Supported Libraries
Custom Configuration
import pg from 'eslint-plugin-postgresql-security';
export default [
{
plugins: { pg },
rules: {
'pg/no-unsafe-query': 'error',
'pg/no-select-all': 'off', // Disable if needed
},
},
];💡 What You Get
- PostgreSQL-specific rules: Catches pg driver anti-patterns that generic linters miss
- LLM-optimized messages: Structured 2-line errors with CWE + fixes that AI assistants can apply
- Connection safety: Prevents leaks, double releases, and transaction race conditions
- SQL security: SQL injection, search_path hijacking, file access via COPY
- Performance patterns: N+1 queries, SELECT *, bulk operation suggestions
Every rule produces a structured error message:
src/db.ts
42:15 error 🔒 CWE-89 OWASP:A03-Injection CVSS:9.8 | Unsafe query detected | CRITICAL
Fix: Use parameterized query: client.query('SELECT * FROM users WHERE id = $1', [userId])📦 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 | 🧠 | 💼 | ⚠️ | 🔧 | 💡 | 🚫 |
|---|---|---|---|---|---|---|---|---|---|---|
| check-query-params | CWE-89 | Ensures the number of placeholders in SQL queries matches the provided parameters. | 🟢 | ⚠️ | ||||||
| no-batch-insert-loop | CWE-400 | Prevents INSERT/UPDATE/DELETE queries inside loops (N+1 query anti-pattern). | 🟢 | ⚠️ | ||||||
| no-floating-query | CWE-252 | Ensures query promises are awaited or handled. | 🟢 | 💼 | ||||||
| no-hardcoded-credentials | CWE-798 | Prevents hardcoded passwords and connection strings in PostgreSQL client initialization. | 🟢 | 💼 | ||||||
| no-insecure-ssl | CWE-295 | Prevents disabling SSL certificate validation in PostgreSQL connections. | 🟢 | 💼 | ||||||
| no-missing-client-release | CWE-772 | Ensures acquired pool clients are released back to the pool. | 🟢 | 💼 | ||||||
| no-select-all | CWE-693 | Discourages SELECT in favor of explicit column lists. | 🟢 | ⚠️ | ||||||
| no-transaction-on-pool | CWE-362 | Prevents running transaction commands directly on pool (must use dedicated client). | 🟢 | 💼 | ||||||
| no-unsafe-copy-from | CWE-73 | A03:2021 | Prevents COPY FROM with file paths (should use STDIN for safe client-side data loading). | 🟢 | 💼 | |||||
| no-unsafe-query | CWE-89 | SQL injection is one of the most critical security vulnerabilities | 🟢 | 💼 | ||||||
| no-unsafe-search-path | CWE-426 | Prevents dynamic SET searchpath queries that could enable schema hijacking. | 🟢 | 💼 | ||||||
| prefer-pool-query | CWE-693 | Suggests using pool.query() for single-shot queries instead of manual connect/release. | 🟢 | ⚠️ | ||||||
| prevent-double-release | CWE-415 | Prevents calling client.release() multiple times on the same client. | 🟢 | 💼 |
🔗 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. | |
eslint-plugin-reliability | Runtime stability and error safety. |
⭐ 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.