FixMap v0.7.0

Added

• Added bounded, explainable definition-site ranking for distinctive task identifiers and exact code or literal fragments, including truncated literals from issue excerpts.
• Added focused regressions for exact literal extraction, generic-identifier noise, and definition-site ranking.

Changed

• Improved the frozen six-repository evaluation from 50% / 83% / 83% top-1/3/5 to 67% / 100% / 100%. The unchanged Zod #5944 case now ranks its fixing regexes.ts file first.

FixMap v0.6.2

Security

• Updated Next.js to 16.2.11 and pinned patched Sharp/libvips and fast-uri releases, clearing all high-severity production audit findings.
• Added a production audit gate that fails CI on high or critical advisories. The remaining two moderate findings come from the MCP SDK's unused HTTP static-file adapter; FixMap exposes only the SDK's stdio transport and does not import or run that adapter.

FixMap v0.6.1

Fixed

• Shortened the MCP Registry description to its 100-character limit so the official registry publication can complete.
• Added a repository CI check and release preflight validation for MCP server metadata, preventing registry-only constraints from failing after npm packages have already published.

FixMap v0.5.1

Added

• Root GitHub Action metadata enables the shorter uses: aryamthecodebreaker/FixMap@v0.5.1 install path and makes the repository eligible for a Marketplace listing.

Fixed

• File mentions now bridge JavaScript build paths to their TypeScript source equivalents, so a task naming core/Ky.js can rank source/core/Ky.ts as explicit context.
• Import-graph proximity can no longer boost a neighbor above the higher-scoring seed that supplied the evidence.
• Example/demo files and TypeScript declaration files are deprioritized for runtime implementation tasks, while tasks that explicitly target them keep the normal ranking behavior.
• Evaluation failures now print hit rates as real percentages instead of decimal fractions followed by a percent sign.

Changed

• The frozen six-repository evaluation now measures 50% top-1, 83% top-3, and 83% top-5, up from 33% / 33% / 67% on v0.5.0. Zod #5944 remains the documented miss.
• Exact per-case external rankings are now checked in, and scheduled/release runs fail if live output drifts from that reviewed artifact.
• Package and MCP descriptions now lead with deterministic local-first analysis and public GitHub URL support.
• Release publishing now gates on the external evaluation and builds the GitHub release body from the matching changelog section.

FixMap v0.5.0

What's Changed

• fix: declare repository metadata required by npm provenance by @aryamthecodebreaker in #51
• docs: refresh the launch kit for the v0.4.0 star push by @aryamthecodebreaker in #53
• release: v0.4.1 — publish to the official MCP Registry by @aryamthecodebreaker in #55
• feat: add one-command public GitHub repository analysis by @aryamthecodebreaker in #56

Full Changelog: v0.4.0...v0.5.0

v0.4.0 — import-graph proximity, gated-test diagnostics, cross-repo evaluation

Added

• Import-graph proximity: files one or two static import edges from a high-confidence context file are boosted with inspectable reasons (imported by ranked file <path>). Relative specifiers only, compiled .js → .ts mappings resolved, bounded for large repositories. (#12)
• Gated-test visibility: changed test files always appear in the test route's related files, and env-gated suites (describe.skipIf(...)) emit a gated-test-skipped diagnostic naming the enabling variable — no more silently skipped integration coverage. (#33)
• pnpm + Turborepo example proving nearest-package script routing, guarded by a report-drift smoke check in CI. (#14)
• Scanner performance baseline in docs/BENCHMARKS.md from a deterministic generated-repo harness; CI asserts correctness, never wall-clock timing. (#15)
• Cross-repository evaluation: six real fixed issues (Express, Axios, debug, ky, Zod, Pino) pinned to exact commits, honest top-1/3/5 hit rates (33% / 67% / 67%), weekly workflow. (#13)
• Reproducible animated CLI demo in the README, rendered from live CLI output. (#17)
• Marketplace branding metadata for the GitHub Action. (#16)

Fixed

• Files explicitly named in the task now rank into context files (including test files); JS/TS reserved words no longer count as content matches. (#22)
• Diff risk severity is grounded in changed files — an unrelated auth file surfaced by weak context matching can no longer produce a false high-severity claim. (#35)
• The GitHub Action stays green on read-only tokens (forked pull requests): it warns and keeps the report in the step summary instead of failing the job. Validated in a live read-only acceptance run. (#16)
• The Action runtime moved to Node 24 ahead of GitHub's Node 20 deprecation. (#48)

Changed

• README versioned prose is now version-neutral with changelog pointers; the Action example pins the latest release tag. (#34)
• The site got a refined editorial redesign.

Install: npx @aryam/fixmap plan --issue "..." · Action: uses: aryamthecodebreaker/FixMap/packages/action@v0.4.0

v0.3.1 — scanner and ranking quality fixes

Published to npm as @aryam/fixmap@0.3.1 and @aryam/fixmap-core@0.3.1 before this release was cut, and verified cold: npx -y @aryam/fixmap@0.3.1 mcp starts and serves fixmap_plan correctly.

Fixed

• A nonexistent --repo path now fails with a clear error and nonzero exit instead of an empty success report; the MCP tool returns an error result for the same case (#21).
• Repository scans respect .gitignore in git repositories via git ls-files, so ignored build output such as .vercel/ no longer outranks source files (#23).
• Common stop words and stem fragments no longer count as content matches, deployment-related tasks rank root configuration such as vercel.json and package.json, and lockfiles are excluded from ranking (#22).
• An unresolvable diff ref with no --issue fallback now exits nonzero instead of an empty success report (#25).
• Working-tree diff specs such as --diff HEAD include untracked files in changed context (#26).

Added

• npm publish workflow using trusted publishing with provenance (#29).
• Package READMEs on the npm registry pages (#20).

Full changelog: v0.3.0...v0.3.1

v0.3.0 — MCP server mode

FixMap now runs as a Model Context Protocol server, so coding agents can request a repo plan themselves.

Added

• MCP server mode: fixmap mcp runs an MCP server over stdio, exposing the fixmap_plan tool to Claude Code, Cursor, Windsurf, and other MCP clients.

  claude mcp add fixmap -- npx -y @aryam/fixmap mcp

• buildFixMapReport in @aryam/fixmap-core: one call from task input to a complete report, now shared by the CLI, the GitHub Action, and the MCP server.

Everything runs locally over stdio; no repository content leaves the machine.

Full changelog: v0.2.1...v0.3.0

FixMap v0.2.1

FixMap v0.2.1

This patch publishes the first installable FixMap packages under the verified npm account scope.

Install

npx @aryam/fixmap plan --issue "password reset emails fail"

Packages

• @aryam/fixmap — CLI
• @aryam/fixmap-core — scanner, ranker, routing, and report library

The engine and web experience are unchanged from v0.2.0; this patch corrects the distribution scope and install links.

FixMap v0.2.0

FixMap v0.2.0

A launch-readiness release focused on useful first-run output, transparent evaluation, and distribution.

Highlights

• quieter file-kind-aware ranking with confidence levels
• workspace-aware test routing for npm, pnpm, Yarn, and Bun
• explicit diagnostics for invalid diffs and scan limits
• scoped npm package manifests and GitHub Action outputs
• checked-in ranking evaluation gate
• interactive live demo at https://fixmap-flax.vercel.app
• stable Next.js/React stack, repaired ESLint, and zero audited vulnerabilities

See CHANGELOG.md for the complete release notes.