CodeGuard

Appearance

Release history

What's New in CodeGuard

Explore the latest features, improvements, and fixes across every CodeGuard release.

Latest release

CodeGuard 0.6.0-beta.0

Developer Experience & AI Integration

Beta

Adds live watch mode to the CLI and two MCP prompt templates. All analyzers, rule IDs, the six MCP tools, and CLI exit codes are unchanged.

  • Live watch mode
  • Automatic project re-analysis
  • Configurable debounce
  • MCP review_project prompt
  • MCP explain_diagnostics prompt
  • Synchronized CLI and MCP versions
  • Improved watch reporting
  • Expanded automated testing

New features

  • codeguard watch [path] [--debounce <ms>] runs an initial analysis, then re-analyzes the project after source changes with debounced, non-overlapping runs.
  • The MCP server registers review_project and explain_diagnostics prompt templates. They are plain instructions for a compatible client; CodeGuard contains no AI model and does not fix code automatically.

Improvements

  • The terminal and watch reporters share one diagnostic formatter; codeguard check output is unchanged.
  • The CLI --version and the MCP server version are read from the package manifest, so they stay synchronized.
  • The package smoke test now covers watch mode, MCP prompts, and rejection of invalid prompt arguments against the installed tarball.
  • Added automated tests for watch mode, the scheduler, path filtering, MCP prompts, and the MCP version.

Bug fixes

  • The MCP server no longer reports a stale hardcoded version.

Security

  • Watch mode applies the same ignore rules as check, so environment, key, and credential-style files are never watched.
  • Watch mode does not follow symlinked directories and bounds the number of watched directories and pending changes.
  • Prompt arguments are validated: codes are restricted to a safe character set, and file paths must be project-relative without ... Prompts contain no project source or credential values.

npm package for 0.6.0-beta.0 (opens in a new tab)Git tag for 0.6.0-beta.0 (opens in a new tab)

Earlier releases

  1. CodeGuard 0.5.0-beta.1

    Official website links

    Beta

    A metadata and documentation update that points the package and README at the official documentation website.

    Improvements

    • The package homepage now points to the official documentation website.
    • The README and site footer link to the official website and npm package.

    npm package for 0.5.0-beta.1 (opens in a new tab)

  2. CodeGuard 0.5.0-beta.0

    Initial public beta

    Beta

    The first public beta of `codeguard-local`, published under the npm `beta` dist-tag, with the 0.4.0 analyzers, CLI, JSON output, and six-tool MCP server.

    New features

    • Global installation with npm install -g codeguard-local@beta.
    • CLI and MCP setup documentation for beta users.

    Improvements

    • Preserves the 0.4.0 analyzer, CLI, JSON, and six-tool MCP behavior.

    Bug fixes

    • Resolved cross-platform CI failures on Linux, Windows, and macOS.

    npm package for 0.5.0-beta.0 (opens in a new tab)Git tag for 0.5.0-beta.0 (opens in a new tab)

  3. CodeGuard 0.4.0

    Release preparation

    Development milestone

    A development milestone that prepared the project for public release. It was not published to npm.

    New features

    • Node.js 24 cross-platform GitHub Actions CI for Linux, Windows, and macOS.
    • Installed-tarball package smoke testing, including real MCP protocol checks.
    • Reproducible synthetic-project benchmark tooling.
    • VitePress documentation site with user, security, contributor, and release documentation.

    Improvements

    • Bounded directory traversal replaces eager file discovery, with caps on scan depth, directory entries, and supported files.
    • Upgraded the lint toolchain to ESLint 10 and pinned VitePress to a patched Vite release.

    Security

    • MCP diagnostic output is hardened against credential-like string literal disclosure.

  4. CodeGuard 0.3.0

    MCP server

    Development milestone

    A development milestone that introduced the MCP server. It was not published to npm.

    New features

    • Stdio MCP server built on the official MCP TypeScript SDK with six analysis tools.
    • Single-file analysis with project context.
    • Structured MCP results.

    Improvements

    • Bounded MCP diagnostics.
    • Configuration validation upgraded to Zod 4.

    Security

    • A canonical project root is required, and file paths are validated against it.

    Git tag for 0.3.0 (opens in a new tab)

  5. CodeGuard 0.2.0

    Advanced static analysis

    Development milestone

    A development milestone that added JavaScript, security, and architecture analysis. It was not published to npm.

    New features

    • JavaScript and JSX diagnostics through the TypeScript Compiler API.
    • Architecture rules ARCH001–ARCH002.
    • Per-rule configuration that keeps boolean analyzer switches working.
    • JSON and terminal reporting for shared diagnostics.

    Improvements

    • File discovery moved to tinyglobby.
    • Node.js 24 adopted as the supported runtime.

    Security

    • Deterministic security rules SEC001–SEC005.

    Git tag for 0.2.0 (opens in a new tab)

  6. CodeGuard 0.1.0

    Foundation

    Development milestone

    The first development milestone. It was not published to npm.

    New features

    • TypeScript CLI with a project scanner and detector, configuration loader, and analysis engine.
    • TypeScript analyzer.
    • Terminal and JSON reporting.

Development milestones are documented in the project changelog but were never published to npm. Published versions are 0.5.0-beta.0 and later, and dates are npm publication dates. Full notes are in the changelog.