Repo analysis for coding agents with ranked files, dependency maps, and task-scoped context.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"cartograph": {
"args": [
"mcp"
],
"command": "cartograph"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Cartograph is task-shaped repo context for coding agents. It ships a CLI, an MCP server, user-scope install adapters for Claude Code and OpenClaw, and packaged agent assets for documentation-heavy workflows.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools
Manage Supabase projects — databases, auth, storage, and edge functions
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for io.github.anthony-maio/cartograph and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Cartograph is task-shaped repo context for coding agents. It ships a CLI, an MCP server, user-scope install adapters for Claude Code and OpenClaw, and packaged agent assets for documentation-heavy workflows.
@anthony-maio/cartographio.github.anthony-maio/cartographcartograph.making-minds.aiInstead of dumping an entire repository into context, Cartograph ranks the files that matter, maps dependencies, caches structured artifacts, and lets the next tool or agent pick up from those artifacts.
The primary workflow is:
analyze to map the repopacket to prepare the workcontext to load the minimum fileswiki, host installs, and benchmarks are secondary surfaces built around that core path.
npm install
npm run build
For global use from npm:
npm install -g @anthony-maio/cartograph
For MCP host discovery via the official registry:
io.github.anthony-maio/cartographFor Claude Code plugin install from this public repo:
/plugin marketplace add anthony-maio/cartograph
/plugin install cartograph@making-minds-tools
For global use from a local checkout:
npm install -g .
See CONTRIBUTING.md for the development workflow and SECURITY.md for vulnerability reporting.
This repo also acts as a Claude Code plugin marketplace. The cartograph plugin bundles:
/cartograph:analyze, /cartograph:context, /cartograph:wikiuse-cartograph and repo-surveyor skillsrepo-scout, dependency-tracer, context-picker, api-surface-writer, and wiki-writerInstall it with:
/plugin marketplace add anthony-maio/cartograph
/plugin install cartograph@making-minds-tools
If you only remember one thing, remember this:
cartograph analyze <repo> --static
cartograph packet <repo> --type <type> --task "<task>"
cartograph context <repo> --task "<task>" --json
analyze maps the repo and tells you what matters.packet turns a concrete job into a reusable working artifact.context gives the next agent the smallest useful file set.cartograph analyze <repo> [options]
cartograph packet <repo> --type <type> --task "<task>" [--changed <paths...>]
cartograph context <repo> --task "<task>" [options]
cartograph wiki <repo> [options]
cartograph export <run-id> --to <path> [--artifact <name>]
cartograph install <claude|openclaw|mcp>
cartograph uninstall <claude|openclaw|mcp>
cartograph doctor [target] [--json]
cartograph mcp
Legacy compatibility still works:
cartograph <repo> --static
cartograph <repo> -c "trace auth flow"
# Map the repo
cartograph analyze ./my-project --static
# Prepare a concrete job
cartograph packet ./my-project --type bug-fix --task "fix auth refresh bug" --changed src/auth/service.ts tests/auth/service.test.ts
# Load the minimum file set for that job
cartograph context ./my-project --task "add user authentication" --json
# Force embedded snippets when you really want them
cartograph analyze ./my-project --static --json --include-contents
# Full wiki output
cartograph wiki ./my-project -p gemini -k $CARTOGRAPH_API_KEY -o wiki.md
# Export a cached artifact to an explicit path
cartograph export run-abc123 --to ./artifacts/wiki.md
# Run the MCP server directly
cartograph mcp
For small repos, analyze --static --json now defaults to compact output instead of embedding top-file contents. That keeps ti