Skip to main content
1128 releases · 66 packages

Changelog

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

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

eslint-plugin-nestjs-security 4.2.0

  • Featurerequire-upload-size-limit, and require-throttler now asks for a bound guard

npm install --save-dev eslint-plugin-nestjs-security@4.2.0

oxlint-plugin-nestjs-security 4.1.1

  • Dependenciesupdated workspace dependencies: eslint-plugin-nestjs-security@4.1.1

npm install --save-dev oxlint-plugin-nestjs-security@4.1.1

eslint-plugin-nestjs-security 4.1.1

  • Fixno-missing-validation-pipe no longer reports one named scalar

npm install --save-dev eslint-plugin-nestjs-security@4.1.1

oxlint-plugin-nestjs-security 4.1.0

  • Dependenciesupdated workspace dependencies: eslint-plugin-nestjs-security@4.1.0

npm install --save-dev oxlint-plugin-nestjs-security@4.1.0

eslint-plugin-nestjs-security 4.1.0

  • FeatureNestJS 12 — Standard Schema validation and serialization, returned web responses
  • Fixinstall alongside NestJS 12

npm install --save-dev eslint-plugin-nestjs-security@4.1.0

oxlint-plugin-secure-coding 6.1.0

  • Dependenciesupdated workspace dependencies: eslint-plugin-secure-coding@6.1.0

npm install --save-dev oxlint-plugin-secure-coding@6.1.0

eslint-plugin-secure-coding 6.1.0

  • Featureno-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

eslint-devkit 2.0.3

  • Maintenancevendor the AST and rule type declarations devkit uses

npm install --save-dev @interlace/eslint-devkit@2.0.3

oxlint-plugin-node-security 6.0.3

  • Dependenciesupdated workspace dependencies: eslint-plugin-node-security@6.0.3

npm install --save-dev oxlint-plugin-node-security@6.0.3

eslint-plugin-node-security 6.0.3

  • Fixdetect-non-literal-fs-filename reads /* global */ directives the way ESLint does

npm install --save-dev eslint-plugin-node-security@6.0.3

oxlint-plugin-node-security 6.0.2

  • Dependenciesupdated workspace dependencies: eslint-plugin-node-security@6.0.2

npm install --save-dev oxlint-plugin-node-security@6.0.2

eslint-plugin-node-security 6.0.2

  • Fixdetect-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

oxlint-plugin-secure-coding 6.0.2

  • Dependenciesupdated workspace dependencies: eslint-plugin-secure-coding@6.0.2

npm install --save-dev oxlint-plugin-secure-coding@6.0.2

eslint-plugin-secure-coding 6.0.2

  • Fixdetect-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

oxlint-plugin-postgresql-security 3.0.2

  • Dependenciesupdated workspace dependencies: eslint-plugin-postgresql-security@3.0.2

npm install --save-dev oxlint-plugin-postgresql-security@3.0.2

oxlint-plugin-vercel-ai-security 3.0.2

  • Dependenciesupdated workspace dependencies: eslint-plugin-vercel-ai-security@3.0.2

npm install --save-dev oxlint-plugin-vercel-ai-security@3.0.2

eslint-plugin-postgresql-security 3.0.2

  • FixInternal: test property names with the null-safe 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.
  • Dependenciesupdated workspace dependencies: @interlace/eslint-devkit@2.0.2

npm install --save-dev eslint-plugin-postgresql-security@3.0.2

eslint-plugin-vercel-ai-security 3.0.2

  • FixInternal: test property names with the null-safe 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.
  • Dependenciesupdated workspace dependencies: @interlace/eslint-devkit@2.0.2

npm install --save-dev eslint-plugin-vercel-ai-security@3.0.2

eslint-devkit 2.0.2

  • FixInternal: test property names with the null-safe 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