eslint-plugin-vercel-ai-security 1.3.8 → 1.3.10

package/CHANGELOG.md

@@ -1,3 +1,28 @@
+## 1.3.10
+
+### Patch Changes
+
+- [#294](https://github.com/ofri-peretz/eslint/pull/294) [`659f6dc`](https://github.com/ofri-peretz/eslint/commit/659f6dc0181b03b675f72b5949fcf123dd066358) Thanks [@ofri-peretz](https://github.com/ofri-peretz)! - Rewrite `description` and `keywords` on every published package for npm search discovery. npm ranks on name, description, and keywords, and the registry only picks up these fields at publish — so this is metadata-only and takes effect for each package on its next release.
+
+  **Descriptions now lead with the search phrase.** Every one starts `ESLint plugin for <the thing you'd search>` instead of a brand-first or category-first framing, and names the concrete vulnerabilities the plugin actually detects. Three were corrected while doing so:
+
+  - `eslint-plugin-import-next` claimed "100x faster no-cycle detection". No 100x measurement exists: `CLAIMS.md` records **3.1x end-to-end** (8x in pure rule execution) on a 5,483-file React codebase, and the highest number in any benchmark result is 54.9x on the synthetic corpus. The description now states the real-codebase figure.
+  - `eslint-plugin-secure-coding` claimed SQL injection, XSS and CSRF coverage — none of which are its rules. It now names what it does detect: LDAP, XPath, XXE, GraphQL and template injection, unsafe deserialization, ReDoS, missing authentication, and PII in logs.
+  - `eslint-plugin-secure-coding` ("89 rules") and `eslint-plugin-react-a11y` ("37 rules") hard-coded rule counts that had drifted from reality. Counts are generated into `interlace-numbers.json`; hand-typed copies are removed rather than corrected.
+
+  **Keywords now match the vocabulary of the plugins that rank.** `eslint-plugin-security`, `eslint-plugin-jsx-a11y`, `eslint-plugin-n` and `eslint-plugin-import` all carry the `eslint` / `eslintplugin` / `eslint-plugin` trio — six of our packages were missing `eslintplugin`, and every one now carries all three plus `static-analysis`, `linting` and `code-quality`. Security plugins add `sast`, `appsec` and `vulnerability`; `node-security` and `secure-coding` also carry `nodesecurity`, the exact keyword `eslint-plugin-security` ranks on. Each plugin gained the CWE identifiers and attack names for what it detects (`cwe-78` command injection, `cwe-22` path traversal, `cwe-89` SQL injection, `cwe-79` XSS, `cwe-347` JWT algorithm confusion, `cwe-352` CSRF, `cwe-943` NoSQL injection), and `node-security` gained the crypto vocabulary it had been missing entirely despite absorbing the crypto rule set (`crypto`, `cryptography`, `weak-hash`, `md5`, `sha1`, `timing-attack`).
+
+  No rule behavior, exports, or configuration changes.
+
+- Updated dependencies [[`e1cdf83`](https://github.com/ofri-peretz/eslint/commit/e1cdf83e3db761907f0ab06f7fc6c1f1da7513a5), [`659f6dc`](https://github.com/ofri-peretz/eslint/commit/659f6dc0181b03b675f72b5949fcf123dd066358)]:
+  - @interlace/eslint-devkit@1.4.3
+
+## 1.3.9
+
+### Patch Changes
+
+- [#277](https://github.com/ofri-peretz/eslint/pull/277) [`d1ad332`](https://github.com/ofri-peretz/eslint/commit/d1ad332cc7366887482b288bcf65098d425501d0) Thanks [@ofri-peretz](https://github.com/ofri-peretz)! - Accept AI SDK v5+ idioms: `stopWhen` (e.g. `stopWhen: stepCountIs(5)`) now satisfies require-max-steps, and `maxOutputTokens` (v5 rename of `maxTokens`) satisfies require-max-tokens — fixing false positives on v5/v7 code.
+
 ## 1.3.8
 
 ### Patch Changes

package/README.md

@@ -136,8 +136,8 @@ See the [ESLint Version Support Policy](../../docs/ESLINT_VERSION_SUPPORT.md) fo
 | [require-audit-logging](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-audit-logging?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-778 |  |  | This rule identifies AI SDK calls that aren't preceded by logging statements | 🟢 |  |  |  |  |  |
 | [require-embedding-validation](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-embedding-validation?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-20 |  |  | This rule identifies code patterns where embeddings are stored in vector databases without validation. | 🟢 |  |  |  |  |  |
 | [require-error-handling](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-error-handling?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-755 |  |  | This rule identifies AI SDK calls that aren't wrapped in try-catch blocks | 🟢 |  |  |  |  |  |
-| [require-max-steps](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-max-steps?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-834 |  |  | This rule identifies AI SDK calls that use tools but don't specify a maxSteps limit | 🟢 |  |  |  |  |  |
-| [require-max-tokens](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-max-tokens?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-770 |  |  | This rule identifies AI SDK calls that don't specify a maxTokens limit | 🟢 |  |  |  |  |  |
+| [require-max-steps](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-max-steps?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-834 |  |  | This rule identifies AI SDK calls that use tools but don't specify a step limit (maxSteps or stopWhen) | 🟢 |  |  |  |  |  |
+| [require-max-tokens](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-max-tokens?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-770 |  |  | This rule identifies AI SDK calls that don't specify a token limit (maxTokens or maxOutputTokens) | 🟢 |  |  |  |  |  |
 | [require-output-filtering](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-output-filtering?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-200 |  |  | This rule identifies tool execute functions that return raw data from data sources (databases, APIs, file s… | 🟢 |  |  |  |  |  |
 | [require-output-validation](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-output-validation?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-707 |  |  | This rule identifies code patterns where AI-generated output is displayed to users without validation or fa… | 🟢 |  |  |  |  |  |
 | [require-rag-content-validation](https://eslint.interlace.tools/docs/security/plugin-vercel-ai-security/rules/require-rag-content-validation?utm_source=github&utm_medium=referral&utm_campaign=eslint-plugin-vercel-ai-security) | CWE-74 |  |  | This rule identifies code patterns where content retrieved from vector stores or document retrieval systems… | 🟢 |  |  |  |  |  |

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "eslint-plugin-vercel-ai-security",
-  "version": "1.3.8",
-  "description": "Security-focused ESLint plugin for Vercel AI SDK. SDK-aware rules for generateText, streamText, tools, and streaming patterns with full type knowledge.",
+  "version": "1.3.10",
+  "description": "ESLint plugin for Vercel AI SDK security — detects prompt injection, system-prompt leaks, hardcoded API keys, and unvalidated model output in generateText and streamText.",
   "type": "commonjs",
   "main": "./src/index.js",
   "types": "./src/index.d.ts",
@@ -43,27 +43,35 @@
   ],
   "keywords": [
     "eslint",
-    "eslint-plugin",
     "eslintplugin",
-    "interlace-security",
+    "eslint-plugin",
+    "static-analysis",
+    "linting",
+    "code-quality",
     "security",
+    "sast",
+    "appsec",
+    "vulnerability",
+    "owasp",
+    "cwe",
+    "interlace-security",
     "vercel",
     "vercel-ai",
+    "vercel-ai-sdk",
     "ai-sdk",
-    "generateText",
-    "streamText",
+    "ai-security",
     "llm",
+    "llm-security",
+    "generative-ai",
     "prompt-injection",
-    "owasp",
     "owasp-llm-top-10",
-    "cwe",
-    "vulnerability",
+    "rag",
+    "tool-calling",
+    "generateText",
+    "streamText",
     "llm-optimized",
     "ai-assistant",
-    "typescript",
-    "linting",
-    "code-quality",
-    "static-analysis"
+    "typescript"
   ],
   "engines": {
     "node": ">=18.0.0"
@@ -78,7 +86,7 @@
   },
   "dependencies": {
     "tslib": "^2.3.0",
-    "@interlace/eslint-devkit": "^1.4.2"
+    "@interlace/eslint-devkit": "^1.4.3"
   },
   "devDependencies": {
     "@ai-sdk/openai": "^4.0.16",

package/src/index.js

@@ -152,7 +152,7 @@ exports.rules = {
 exports.plugin = {
     meta: {
         name: 'eslint-plugin-vercel-ai-security',
-        version: '1.3.8',
+        version: '1.3.10',
     },
     rules: exports.rules,
 };

package/src/rules/require-max-steps/index.js

@@ -30,10 +30,10 @@ exports.requireMaxSteps = (0, eslint_devkit_1.createRule)({
                 cwe: 'CWE-834',
                 owasp: 'A05:2021',
                 cvss: 6.5,
-                description: '{{function}} with tools is missing maxSteps. Without a limit, tool calls can loop indefinitely.',
+                description: '{{function}} with tools is missing a step limit. Without a limit, tool calls can loop indefinitely.',
                 severity: 'MEDIUM',
                 compliance: ['SOC2'],
-                fix: 'Add maxSteps option: {{function}}({ ..., maxSteps: 5 })',
+                fix: 'Add a step limit: {{function}}({ ..., stopWhen: stepCountIs(5) }) (v5+) or maxSteps: 5 (v4)',
                 documentationLink: 'https://sdk.vercel.ai/docs/ai-sdk-core/tools-and-tool-calling#multi-step-calls-using-stopwhen',
             }),
         },
@@ -81,7 +81,7 @@ exports.requireMaxSteps = (0, eslint_devkit_1.createRule)({
                 // Only check for maxSteps if tools are present
                 if (!hasTools)
                     return;
-                // Check if maxSteps is present
+                // Check if a step limit is present: maxSteps (v4) or stopWhen (v5+, e.g. stopWhen: stepCountIs(5))
                 const hasMaxSteps = optionsArg.properties.some(prop => {
                     if (prop.type !== 'Property')
                         return false;
@@ -90,7 +90,8 @@ exports.requireMaxSteps = (0, eslint_devkit_1.createRule)({
                         : prop.key.type === 'Literal'
                             ? String(prop.key.value)
                             : null;
-                    return keyName === 'maxSteps' || keyName === 'max_steps';
+                    // ponytail: any stopWhen counts — statically proving it bounds steps (arrays, custom conditions) isn't worth it; documented FN
+                    return keyName === 'maxSteps' || keyName === 'max_steps' || keyName === 'stopWhen';
                 });
                 if (!hasMaxSteps) {
                     context.report({

package/src/rules/require-max-tokens/index.js

@@ -30,10 +30,10 @@ exports.requireMaxTokens = (0, eslint_devkit_1.createRule)({
                 cwe: 'CWE-770',
                 owasp: 'A05:2021',
                 cvss: 6.5,
-                description: '{{function}} call without maxTokens limit can lead to excessive resource consumption',
+                description: '{{function}} call without a token limit can lead to excessive resource consumption',
                 severity: 'MEDIUM',
                 compliance: ['SOC2'],
-                fix: 'Add maxTokens option: {{function}}({ maxTokens: 4096, ... })',
+                fix: 'Add a token limit: {{function}}({ maxOutputTokens: 4096, ... }) (v5+) or maxTokens (v4)',
                 documentationLink: 'https://sdk.vercel.ai/docs/ai-sdk-core/generating-text',
             }),
         },
@@ -81,7 +81,7 @@ exports.requireMaxTokens = (0, eslint_devkit_1.createRule)({
                 if (!optionsArg || optionsArg.type !== 'ObjectExpression') {
                     return;
                 }
-                // Check if maxTokens is present
+                // Check if a token limit is present: maxTokens (v4) or maxOutputTokens (v5+ rename)
                 const hasMaxTokens = optionsArg.properties.some(prop => {
                     if (prop.type !== 'Property')
                         return false;
@@ -90,7 +90,7 @@ exports.requireMaxTokens = (0, eslint_devkit_1.createRule)({
                         : prop.key.type === 'Literal'
                             ? String(prop.key.value)
                             : null;
-                    return keyName === 'maxTokens' || keyName === 'max_tokens';
+                    return keyName === 'maxTokens' || keyName === 'max_tokens' || keyName === 'maxOutputTokens';
                 });
                 if (!hasMaxTokens) {
                     context.report({