eslint-plugin-lambda-security 1.2.4 → 1.2.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,46 @@
1
1
  ## [1.2.3] - 2026-02-08
2
2
 
3
+ ## 1.2.5
4
+
5
+ ### Patch Changes
6
+
7
+ - [#220](https://github.com/ofri-peretz/eslint/pull/220) [`ad8416d`](https://github.com/ofri-peretz/eslint/commit/ad8416d4db196bf0b24942ddabbfaefb0cae7bab) Thanks [@ofri-peretz](https://github.com/ofri-peretz)! - Fix runtime crashes when linting realistic AWS Lambda handlers under ESLint 9.
8
+
9
+ The published `1.2.3` tarball was a **stale build**: its rules still threw on the
10
+ generated lambda-ai-corpus handlers, even though source had already been fixed.
11
+ This republishes the corrected build and locks it with a regression test.
12
+ - **`no-error-swallowing`** no longer throws `RangeError: Maximum call stack size
13
+ exceeded`. The old build walked the catch-block AST by hand and recursed through
14
+ the cyclic `node.parent` reference; source now uses `sourceCode.getText()` + a
15
+ regex.
16
+ - **`require-timeout-handling`**, **`no-missing-authorization-check`**, and
17
+ **`no-unbounded-batch-processing`** no longer throw `Error: Unknown class name:
18
+ exit`. They used a grouped `:exit` selector (`'A:exit, B:exit, C:exit'`); ESLint
19
+ only strips the trailing `:exit`, so esquery received a bare `:exit`. Source now
20
+ uses one listener key per node type.
21
+ - `plugin.meta.version` is now read from `package.json` instead of a hardcoded
22
+ string, so a build can no longer mislabel its own version (1.2.3 embedded
23
+ `1.1.0`).
24
+
25
+ - [#213](https://github.com/ofri-peretz/eslint/pull/213) [`391dbe6`](https://github.com/ofri-peretz/eslint/commit/391dbe6b39f78d549379218567cb959649f8c614) Thanks [@ofri-peretz](https://github.com/ofri-peretz)! - Align every security rule's `meta.docs.cvss` to the CVSS its finding actually
26
+ emits. The emitted machine-readable message sources its `CVSS:x` from
27
+ `CWE_MAPPING` via `formatLLMMessage` → `enrichFromCWE`, but the static
28
+ `meta.docs.cvss` documentation field had drifted on 45 rules across these 7
29
+ plugins — e.g. `no-hardcoded-credentials` documented `9.5` while emitting
30
+ `CVSS:9.8` (the value the published article and SARIF/LLM consumers already
31
+ read).
32
+
33
+ This corrects the **documentation metadata only** — no emitted finding changes.
34
+ Locked by `security-cvss-docs-consistency.lock.test.ts` (cross-plugin: every
35
+ security rule's `meta.docs.cvss` must equal the CVSS it emits), the
36
+ `no-hardcoded-credentials` rule lock (real ESLint `Linter` emission), and a
37
+ devkit `enrichFromCWE` contract test pinning `CWE-798 → 9.8`.
38
+
39
+ Follow-up (not in scope): 50 security rules document a CVSS that never appears
40
+ in any emitted message (their messages carry no CWE), and several rules emit the
41
+ generic CWE score where a rule-specific score may be warranted — both change
42
+ emitted output and are separate decisions.
43
+
3
44
  ## 1.2.4
4
45
 
5
46
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eslint-plugin-lambda-security",
3
- "version": "1.2.4",
3
+ "version": "1.2.5",
4
4
  "description": "Security-focused ESLint plugin for AWS Lambda and Middy applications. Detects insecure API Gateway responses, missing security headers, CORS misconfigurations, input validation issues, and more.",
5
5
  "type": "commonjs",
6
6
  "main": "./src/index.js",
package/src/index.js CHANGED
@@ -53,7 +53,7 @@ exports.rules = {
53
53
  exports.plugin = {
54
54
  meta: {
55
55
  name: 'eslint-plugin-lambda-security',
56
- version: '1.2.4',
56
+ version: '1.2.5',
57
57
  },
58
58
  rules: exports.rules,
59
59
  };
@@ -17,7 +17,7 @@ exports.noEnvLogging = (0, eslint_devkit_1.createRule)({
17
17
  url: 'https://github.com/ofri-peretz/eslint/blob/main/packages/eslint-plugin-lambda-security/docs/rules/no-env-logging.md',
18
18
  description: 'Detects logging of process.env which may expose secrets',
19
19
  cwe: 'CWE-532',
20
- cvss: 7.5,
20
+ cvss: 5.3,
21
21
  },
22
22
  hasSuggestions: true,
23
23
  messages: {
@@ -52,7 +52,7 @@ exports.noHardcodedCredentialsSdk = (0, eslint_devkit_1.createRule)({
52
52
  url: 'https://github.com/ofri-peretz/eslint/blob/main/packages/eslint-plugin-lambda-security/docs/rules/no-hardcoded-credentials-sdk.md',
53
53
  description: 'Detects hardcoded AWS credentials in SDK client configurations',
54
54
  cwe: 'CWE-798',
55
- cvss: 9.5,
55
+ cvss: 9.8,
56
56
  },
57
57
  hasSuggestions: true,
58
58
  messages: {
@@ -32,7 +32,7 @@ exports.noSecretsInEnv = (0, eslint_devkit_1.createRule)({
32
32
  url: 'https://github.com/ofri-peretz/eslint/blob/main/packages/eslint-plugin-lambda-security/docs/rules/no-secrets-in-env.md',
33
33
  description: 'Detects secrets directly assigned to environment variables',
34
34
  cwe: 'CWE-798',
35
- cvss: 9.5,
35
+ cvss: 9.8,
36
36
  },
37
37
  hasSuggestions: true,
38
38
  messages: {