oxlint-plugin-nestjs-security 4.2.0
- Dependenciesupdated workspace dependencies:
eslint-plugin-nestjs-security@4.2.0
npm install --save-dev oxlint-plugin-nestjs-security@4.2.0
Every release across the ecosystem, newest first. Each entry links to the pull request that shipped it, and every published version carries the exact command to install it.
1128 releases · page 1 of 57
eslint-plugin-nestjs-security@4.2.0npm install --save-dev oxlint-plugin-nestjs-security@4.2.0
require-upload-size-limit, and require-throttler now asks for a bound guardnpm install --save-dev eslint-plugin-nestjs-security@4.2.0
eslint-plugin-nestjs-security@4.1.1npm install --save-dev oxlint-plugin-nestjs-security@4.1.1
no-missing-validation-pipe no longer reports one named scalarnpm install --save-dev eslint-plugin-nestjs-security@4.1.1
eslint-plugin-nestjs-security@4.1.0npm install --save-dev oxlint-plugin-nestjs-security@4.1.0
npm install --save-dev eslint-plugin-nestjs-security@4.1.0
eslint-plugin-secure-coding@6.1.0npm install --save-dev oxlint-plugin-secure-coding@6.1.0
no-unchecked-loop-condition no longer reports a loop whose bound is a literal, such as for (let cp = 0; cp <= 0x10_ff_ff; cp++). The author chose that number and no input reaches it, so it is not CWE-400. The literal-bound check (largeLoopBound) still exists as an iteration budget, but it is now opt-in: set maxStaticIterations to turn it on. Bounds read from user input, and infinite loops with no exit, are reported as before.npm install --save-dev eslint-plugin-secure-coding@6.1.0
npm install --save-dev @interlace/eslint-devkit@2.0.3
eslint-plugin-node-security@6.0.3npm install --save-dev oxlint-plugin-node-security@6.0.3
detect-non-literal-fs-filename reads /* global */ directives the way ESLint doesnpm install --save-dev eslint-plugin-node-security@6.0.3
eslint-plugin-node-security@6.0.2npm install --save-dev oxlint-plugin-node-security@6.0.2
detect-non-literal-fs-filename honours /* global NAME */ declarations under oxlint too. A path built from a declared global (configuration the environment provides) was silent under ESLint and reported under oxlint, whose scope manager does not read the comment.npm install --save-dev eslint-plugin-node-security@6.0.2
eslint-plugin-secure-coding@6.0.2npm install --save-dev oxlint-plugin-secure-coding@6.0.2
detect-object-injection puts a copy loop's single finding on its first write in source order. It walked the loop body in parser property order, so an if … else copy reported its else write under ESLint and its then write under oxlint.npm install --save-dev eslint-plugin-secure-coding@6.0.2
eslint-plugin-postgresql-security@3.0.2npm install --save-dev oxlint-plugin-postgresql-security@3.0.2
eslint-plugin-vercel-ai-security@3.0.2npm install --save-dev oxlint-plugin-vercel-ai-security@3.0.2
namesOneOf instead of casting propertyName(...) to string. No rule reports differently; a computed key that names nothing is now visibly "no name" rather than a cast that happens to miss.@interlace/eslint-devkit@2.0.2npm install --save-dev eslint-plugin-postgresql-security@3.0.2
namesOneOf instead of casting propertyName(...) to string. No rule reports differently; a computed key that names nothing is now visibly "no name" rather than a cast that happens to miss.@interlace/eslint-devkit@2.0.2npm install --save-dev eslint-plugin-vercel-ai-security@3.0.2
namesOneOf instead of casting propertyName(...) to string. No rule reports differently; a computed key that names nothing is now visibly "no name" rather than a cast that happens to miss.npm install --save-dev @interlace/eslint-devkit@2.0.2