io.github.aryamthecodebreaker/fixmap
NPM · @ARYAM/FIXMAP
Deterministic local-first context and impact maps for coding agents from tasks, issues, and diffs.
Available components
Last scanned (19 hours ago)
Scores higher than 90% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aryamthecodebreaker/FixMap). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 82 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1861 tokens (~265/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −2
- Stability: pass → 0.87 functional
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@aryam/fixmap@0.9.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | aryamthecodebreaker/FixMap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aryamthecodebreaker/FixMap/.github/workflows/publish.yml@refs/tags/v0.9.0 |
| Rekor log index | 2449393824 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:92711824bb20330ab0a82ae7380a1eaa49432539dd67d26dd5b52b2b3aeb959a01a54d378eaee9f61332911da282573bb365b85f857c007addc61459d |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fixmap_compare FixMap compare ~98
Compare an earlier FixMap JSON report with a current report without rescanning. Returns files that entered, left, moved, changed confidence, or stayed unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| current | – | yes | Current FixMap JSON report object or path to a local JSON report file |
| format | string | – | Output format: markdown (default) or json, case-insensitive |
| previous | – | yes | Earlier FixMap JSON report object or path to a local JSON report file |
No output schema declared.
No examples provided.
fixmap_context FixMap context ~369
Select task-aware source ranges from FixMap's primary and impact files within a deterministic source-token budget. Use this after Plan and before editing; it does not call a model or execute repository code.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Base git ref to diff against when diff is not given |
| budget | number | – | Estimated source-token budget, a whole number from 256 to 200000; default 10000 |
| diff | string | – | Git diff spec, such as main...HEAD |
| exclude | array | – | Path patterns to leave out of ranking, gitignore-flavored, such as "apps/web" or "docs/**". A .fixmapignore file in the repository is applied as well. |
| format | string | – | Output format: markdown (default) or json, case-insensitive |
| head | string | – | Head git ref, defaults to HEAD |
| includeUntracked | boolean | – | With workingTree, include untracked files |
| issue | string | – | Issue text, task description, or public GitHub issue URL. A GitHub issue URL supplies the task and infers repo when repo is omitted. |
| limit | number | – | Maximum context files to return, 1 to 20, default 8. Lower it when context budget matters: the useful signal is usually the top one to three. |
| noCache | boolean | – | Bypass the exact-state repository scan cache |
| ref | string | – | Branch or tag to scan when repo is a remote GitHub URL |
| repo | string | – | Local path or public GitHub HTTPS repository URL, defaults to the server working directory. GitHub URLs support issue-only analysis and are removed after scanning. |
| workingTree | boolean | – | Map staged and unstaged tracked changes against HEAD |
No output schema declared.
No examples provided.
fixmap_doctor FixMap doctor ~43
Check the running FixMap installation for stale or shadowed binaries.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format: markdown (default) or json, case-insensitive |
No output schema declared.
No examples provided.
fixmap_explain FixMap explain ~327
Answer why one specific file was ranked where it was, or left out of a plan entirely. Use this when a file you expected is missing from fixmap_plan, or when a ranked file looks wrong: it separates the cases that actually differ — ranked, scored below the cutoff, tied but outside the reported limit, deliberately excluded, or never scanned — instead of leaving you to guess. Needs a local checkout, because it re-ranks the repository rather than reading a saved report.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Base git ref to diff against when diff is not given |
| diff | string | – | Git diff spec, such as main...HEAD |
| exclude | array | – | The same exclusion patterns used for the plan |
| format | string | – | Output format: markdown (default) or json, case-insensitive |
| head | string | – | Head git ref, defaults to HEAD |
| includeUntracked | boolean | – | With workingTree, include untracked files |
| issue | string | – | The same task signal used for the plan, so the explanation matches that ranking |
| limit | number | – | Maximum reported context files, 1 to 20 |
| noCache | boolean | – | Bypass the exact-state repository scan cache |
| path | string | yes | Repository-relative path to explain, such as "src/auth/reset-password.ts" |
| repo | string | – | Local repository path, defaults to the server working directory. Remote URLs are not supported. |
| workingTree | boolean | – | Explain against staged and unstaged tracked changes, matching a working-tree plan |
No output schema declared.
No examples provided.
fixmap_graph FixMap graph ~331
Export FixMap's evidence-backed Impact Graph, including import direction, routed tests, and repeated co-change relationships, as Mermaid or JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Base git ref to diff against when diff is not given |
| diff | string | – | Git diff spec, such as main...HEAD |
| exclude | array | – | Path patterns to leave out of ranking, gitignore-flavored, such as "apps/web" or "docs/**". A .fixmapignore file in the repository is applied as well. |
| format | string | – | Output format: mermaid (default) or json, case-insensitive |
| head | string | – | Head git ref, defaults to HEAD |
| includeUntracked | boolean | – | With workingTree, include untracked files |
| issue | string | – | Issue text, task description, or public GitHub issue URL. A GitHub issue URL supplies the task and infers repo when repo is omitted. |
| limit | number | – | Maximum context files to return, 1 to 20, default 8. Lower it when context budget matters: the useful signal is usually the top one to three. |
| noCache | boolean | – | Bypass the exact-state repository scan cache |
| ref | string | – | Branch or tag to scan when repo is a remote GitHub URL |
| repo | string | – | Local path or public GitHub HTTPS repository URL, defaults to the server working directory. GitHub URLs support issue-only analysis and are removed after scanning. |
| workingTree | boolean | – | Map staged and unstaged tracked changes against HEAD |
No output schema declared.
No examples provided.
fixmap_plan FixMap plan ~452
Map an issue, prompt, or git diff to the repository files worth reading first, the test commands most likely to validate a change, and the areas that deserve review attention. Run this before editing code so the change starts from the right context. Provide at least one of issue, diff, base/head, or workingTree. analysis.nextAction carries the single most useful next step for this report. Read it before acting. Treat the result as a starting map, not proof the task is valid: check the analysis block before editing, and when it reports unresolved or unverified identifiers, vague task grounding, an incomplete scan, or a clustered ranking, widen the search or ask for clarification instead of assuming the top-ranked file is correct.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Base git ref to diff against when diff is not given |
| diff | string | – | Git diff spec, such as main...HEAD |
| exclude | array | – | Path patterns to leave out of ranking, gitignore-flavored, such as "apps/web" or "docs/**". A .fixmapignore file in the repository is applied as well. |
| format | string | – | Output format: markdown (default), json, or compact agent, case-insensitive |
| head | string | – | Head git ref, defaults to HEAD |
| includeUntracked | boolean | – | With workingTree, include untracked files |
| issue | string | – | Issue text, task description, or public GitHub issue URL. A GitHub issue URL supplies the task and infers repo when repo is omitted. |
| limit | number | – | Maximum context files to return, 1 to 20, default 8. Lower it when context budget matters: the useful signal is usually the top one to three. |
| noCache | boolean | – | Bypass the exact-state repository scan cache |
| ref | string | – | Branch or tag to scan when repo is a remote GitHub URL |
| repo | string | – | Local path or public GitHub HTTPS repository URL, defaults to the server working directory. GitHub URLs support issue-only analysis and are removed after scanning. |
| workingTree | boolean | – | Map staged and unstaged tracked changes against HEAD |
No output schema declared.
No examples provided.
fixmap_verify FixMap verify ~241
Compare a FixMap plan with the git diff produced after editing. Flags unplanned files, missing test changes, new risk areas, and generated artifacts. Provide the JSON report returned by fixmap_plan plus diff or base/head, and run against a local checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Base git ref when diff is omitted |
| diff | string | – | Git diff spec, such as main...HEAD |
| format | string | – | Output format: markdown (default) or json, case-insensitive |
| head | string | – | Head git ref, defaults to HEAD |
| includeUntracked | boolean | – | With workingTree, include untracked files |
| noCache | boolean | – | Bypass the exact-state repository scan cache |
| repo | string | – | Local repository path, defaults to the server working directory |
| report | – | yes | The FixMap report to verify against, either as the JSON object returned by fixmap_plan or as a path to a local JSON report file such as "./fixmap-report.json". Prefer the path when the plan is large. |
| workingTree | boolean | – | Verify staged and unstaged tracked changes against HEAD |
No output schema declared.
No examples provided.
How do I install the io.github.aryamthecodebreaker/fixmap MCP server?
io.github.aryamthecodebreaker/fixmap runs locally as an npm package, launched with npx -y @aryam/fixmap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @aryam/fixmap
claude mcp add aryamthecodebreaker-fixmap -- npx -y @aryam/fixmap
What is the io.github.aryamthecodebreaker/fixmap MCP server?
io.github.aryamthecodebreaker/fixmap is an MCP server listed in the public MCP registry as io.github.aryamthecodebreaker/fixmap. Deterministic local-first context and impact maps for coding agents from tasks, issues, and diffs. This page covers its npm package (@aryam/fixmap).
Is the io.github.aryamthecodebreaker/fixmap MCP server safe to use?
io.github.aryamthecodebreaker/fixmap scores 86 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.aryamthecodebreaker/fixmap MCP server expose?
io.github.aryamthecodebreaker/fixmap exposes 7 tools: fixmap_plan, fixmap_context, fixmap_graph, fixmap_verify, fixmap_explain, and 2 more. Their descriptions and schemas cost roughly 1,861 tokens of context every time the server is loaded.
Is the io.github.aryamthecodebreaker/fixmap MCP server still maintained?
io.github.aryamthecodebreaker/fixmap is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.aryamthecodebreaker/fixmap MCP server under?
io.github.aryamthecodebreaker/fixmap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.