stalemap 0.4.1

npx stalemap@0.4.1 · npm

• The notes block ends with a line saying where it comes from and how to look further ("Notes by stalemap … run npx stalemap search"), for agents that open a project someone else set up. stalemap check is unaffected.
• Listed in the official MCP Registry as io.github.Umair/stalemap.
• The Claude Code plugin pins stalemap@0.4.1 with a lockfile, and has an icon, README and privacy policy for the Claude plugin directory.

Otherwise the same as 0.4.0, the build tested in held-out v4.

stalemap 0.4.0

npx stalemap@0.4.0 · npm · changelog

This is the build tested in the blind, pre-registered held-out v4 benchmark: 66 tasks from changes released after June 2026, graded by hidden tests.

setup	claude-sonnet-5-5	claude-sonnet-4-5
agent alone	68%	46%
+ plain tsc --noEmit hook	73%	53%
+ stalemap	89%	64%

All four pre-registered comparisons were wins. With claude-sonnet-5-5: +20.7 points vs no help [13.6, 28.3], and +16.4 points vs a plain tsc hook [7.6, 26.0]. Protocol, tasks, review, pilot and results are in bench/heldout-v4/.

What's new

• Guard:
  • It reports everything the project's tsc does, so a plain type-check hook is a subset.
  • When no note explains an error, it shows the matching release-note or upgrade-guide section.
  • It catches moved members that still compile.
• search_changes:
  • It keeps release-note sections and their code together.
  • It fills changelogs that lag the installed version from GitHub releases.
  • It reads the pull request behind terse release-note items.

stalemap 0.3.1

npx stalemap@0.3.1 · npm

Docs only; no change to what stalemap does.

• The npm page's README no longer says the latest release is 0.2.0 or calls 0.3.0's features unreleased.
• README graphics: a banner, a diagram of how it works, and an example of the output.

See 0.3.0 for the last feature release.

stalemap 0.3.0

npx stalemap@0.3.0 · npm · full list in the changelog

New

• search_changes: an MCP tool (and stalemap search <query>) the agent can ask in its own words, such as "resolve alias in next.config", to get the matching type changes, release notes and upgrade-guide notes with their sources.
• stalemap setup --agent cursor|codex|opencode|claude: writes the notes, registers the MCP server and installs the edit-time guard as the agent's post-edit hook. It merges into existing config files and supports --dry-run.
• --guides: notes from upgrade guides, for changes that never reach a type signature (new defaults, moved config options, renamed file conventions).

Better

• The guard asks the project's own TypeScript, including TypeScript 7 through its CLI, so tsconfig.json option errors are reported in every project.
• Notes are selected by what the project uses (imports, members, props, config keys, file names), and the guard's Fix: notes match the error they're about.
• Config files count as usage: tsconfig.json, next.config.*, the Prisma schema, and the Vitest, ESLint, Tailwind and other configs.
• Moved config keys and renamed file conventions (middleware.ts → proxy.ts) are reported even though they still type-check.

Docs

• Comparisons with third-party tools are withdrawn from the README and the benchmark results pending permission.