Skip to main content
interlace
Plugin: mcp-sdk-security

Changelog

Release history and version updates for eslint-plugin-mcp-sdk-security

Generated from the release history

Built from this package's CHANGELOG.md at deploy time, so it matches the version these docs describe. The full cross-package history lives on the changelog.

0.3.0

  • Every rule now runs on files that load the MCP SDK by require, import = or #548
  • DependenciesUpdated internal dependencies

0.2.2

  • Correct the declared ESLint floor: ^8.0.0^8.40.0. #407
  • DependenciesUpdated internal dependencies

0.2.1

  • Ship the JavaScript without tsc's layout. #411
  • DependenciesUpdated internal dependencies

0.2.0

  • Add no-command-injection-in-tool (CWE-78). #397
  • Add no-tool-description-injection (CWE-1427). #396
  • Add no-unvalidated-tool-args (CWE-20). #400
  • DependenciesUpdated internal dependencies

0.1.1

  • Complete the logo row across every published package. #377
  • Fix the ./oxlint subpath export, which pointed at src/oxlint.js — a file no build produces. require('<package>/oxlint') threw MODULE_NOT_FOUND on every published package, while every README documented that exact wiring for oxlint's jsPlugins. The export now points at the build output, dist/src/oxlint.js. #335
  • Fix SDK peer declarations that npm silently ignored #335
  • DependenciesUpdated internal dependencies

0.1.0

  • AI SDK security family + fix the broken oxlint export (#335) (47cde07f) — 2026-08-04
  • complete the logo row across every published package (#377) (85e57a7c) — 2026-08-04

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.