io.github.builditwithgk/repo-cartographer
NPM · REPO-CARTOGRAPHER · SCANNED AUG 6
Maps any repo into an architecture diagram (Mermaid/Graphviz) and enforces architecture rules in CI
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 781 tokens (~130/item across 6 items; 5 tools + 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · repo-cartographer
claude mcp add builditwithgk-repo-cartographer -- npx -y repo-cartographer
codex mcp add builditwithgk-repo-cartographer -- npx -y repo-cartographer
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"builditwithgk-repo-cartographer": {
"type": "local",
"command": [
"npx",
"-y",
"repo-cartographer"
],
"enabled": true
}
}
} openclaw mcp add builditwithgk-repo-cartographer --command npx --arg -y --arg repo-cartographer
mcp_servers:
builditwithgk-repo-cartographer:
command: "npx"
args: ["-y", "repo-cartographer"] {
"mcpServers": {
"builditwithgk-repo-cartographer": {
"command": "npx",
"args": [
"-y",
"repo-cartographer"
]
}
}
} 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.
- 6 Aug 26 +32
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- Package version: 1.0.0 → 1.0.1 functional
- 5 Aug 26 35
First indexed and scored.
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 6 Aug 2026 · Analysed npm/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Deprecated | 95 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
build_import_graph Build import graph ~132
Extract intra-repo import/require relationships for JavaScript/TypeScript and Python. Nodes are files (auto-collapsed to module/directory level for large repos); edges are directed import relationships. Returns JSON. Use this when you need the raw dependency edges — who imports whom — e.g. to reason about coupling, cycles, layering, or the blast radius of a change. Do NOT use it just to draw a picture: generate_diagram returns a ready-to-render draft, and map_repo does the whole flow in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.
generate_diagram Generate diagram ~171
Combine scan + import facts into a DRAFT diagram string — Mermaid flowchart (default) or Graphviz DOT. level 'high' (default) shows modules/directories; 'detail' shows files grouped by module. This is a draft the calling model is expected to refine. Use this when you want to edit or refine the diagram source before rendering (pair with render_diagram to write the HTML afterwards). If no in-between editing is needed, prefer map_repo — it generates AND renders in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | Diagram notation: 'mermaid' (default; renders on GitHub) or 'dot' (Graphviz interop) |
| level | string | — | Diagram granularity (default 'high') |
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.
map_repo Map repository (one-shot) ~192
Point at a folder and get a downloadable architecture diagram in one call: runs scan + import-graph + render internally and returns the HTML path, a facts summary, and the draft diagram source inline. By default writes architecture.html plus the raw source (.mermaid or .dot) into the repo; pass outPath to write elsewhere. Use the granular tools (scan_repo, build_import_graph, generate_diagram, render_diagram) only when you need to compose the steps yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | Diagram notation: 'mermaid' (default; renders on GitHub) or 'dot' (Graphviz interop) |
| level | string | — | Diagram granularity (default 'high') |
| outPath | string | — | Output base path (default: <repo>/architecture); .html and the raw source are written |
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.
render_diagram Render diagram ~161
Write a self-contained, shareable HTML page (renders via CDN: Mermaid, or Viz for Graphviz DOT) plus the raw source file (.mermaid or .dot). Returns the absolute paths written. Use this as the final step after refining a draft from generate_diagram — or to render ANY Mermaid/DOT source, hand-written included. If you have not edited the draft, prefer map_repo, which renders it for you.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | — | Notation of `source` (default 'mermaid') |
| outPath | string | yes | Output path (with or without extension); .html and the raw source siblings are written |
| source | string | yes | Diagram source to render (Mermaid, or DOT when format is 'dot') |
No output schema declared.
No examples provided.
scan_repo Scan repository ~109
Deterministically extract facts from a local repo: programming languages, frameworks/libraries, entry points, top-level modules (with role guesses), and a manifest summary. Returns JSON facts only — no interpretation. Use this when you need repo facts WITHOUT a diagram (e.g. to answer questions about the stack). Prefer map_repo for the one-shot diagram flow; use build_import_graph when you need dependency edges rather than an inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.