io.github.GuangminJu/mellos-mapping
NPM · MELLOS-MAPPING · SCANNED AUG 18
Live layered dependency map for bottom-up development, drawn by the agent in a terminal pane.
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 997 tokens (~199/item across 5 items; 5 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · mellos-mapping
claude mcp add guangminju-mellos-mapping -- npx -y mellos-mapping
codex mcp add guangminju-mellos-mapping -- npx -y mellos-mapping
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"guangminju-mellos-mapping": {
"type": "local",
"command": [
"npx",
"-y",
"mellos-mapping"
],
"enabled": true
}
}
} openclaw mcp add guangminju-mellos-mapping --command npx --arg -y --arg mellos-mapping
mcp_servers:
guangminju-mellos-mapping:
command: "npx"
args: ["-y", "mellos-mapping"] {
"mcpServers": {
"guangminju-mellos-mapping": {
"command": "npx",
"args": [
"-y",
"mellos-mapping"
]
}
}
} 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.
- 18 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +12
- Stability: 0.03 → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Schema quality: 846 → 997 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.18.0 → 0.19.0 functional
- 14 Aug 26 0
- Malware scan: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.14.0 → 0.18.0 functional
- Package version: 0.14.0 → 0.17.0 functional
- Package version: 0.14.0 → 0.16.0 functional
- Package version: 0.14.0 → 0.15.0 functional
- 13 Aug 26 54
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 18 Aug 2026 · Analysed npm/mellos-mapping@0.19.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
mmap_declare Declare map structure ~390
Grow the Mellos map: set the title and diagram kind, add layer bands, lanes and groups (labeled subsystems within ONE band — declare them when a single band grows crowded, roughly five or more nodes in that band; a group must be a strict subset of its band, and a map spread thin across many bands needs none), add nodes, add dependency edges. Declare the whole ghost design up front, then grow it as understanding deepens. Edges must point strictly downward (a node may only use nodes on lower layers); the batch is all-or-nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| edges | array | – | – |
| groups | array | – | – |
| kind | string | – | diagram kind. dev (default) = the live progress ledger with status skins. The rest are documentation diagrams rendered neutrally: architecture (layered components; also fits call graphs and module de… |
| lanes | array | – | vertical columns crossing all bands; declaration order = left-to-right |
| layers | array | – | – |
| nodes | array | – | – |
| page | string | – | page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other… |
| title | string | – | map title, e.g. the feature being built |
No output schema declared.
No examples provided.
mmap_remove Revise the map ~193
Remove edges, nodes, groups and empty layer bands (in that order, all-or-nothing). Removing a node also removes every edge touching it; removing a group merely ungroups its members. Use when the ghost design turns out wrong — the map is a hypothesis, revising it is honest work.
| Name | Type | Req | Description |
|---|---|---|---|
| edges | array | – | – |
| groups | array | – | groups to remove; members stay, merely ungrouped |
| lanes | array | – | lanes to remove; members stay, merely off-lane |
| layers | array | – | bands to remove; must be empty of nodes and groups |
| nodes | array | – | – |
| page | string | – | page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other… |
No output schema declared.
No examples provided.
mmap_setup Configure when maps open ~151
Get or set this project's mapping policy — WHEN the assistant opens a Mellos map. Call with no arguments to read it. If it reports "not set", ask the USER to choose (never pick for them): always = map every structured task — workflows, designs, architecture, technical dependencies; complex = map only medium or complex tasks — several modules, a new subsystem, roughly an hour or more; on-request = map only when the user explicitly asks. Then call again with their choice to persist it. The policy guides you; it never blocks the tools, and an explicit user request for a map always wins.
| Name | Type | Req | Description |
|---|---|---|---|
| policy | string | – | the user's choice to persist; omit to read the current policy |
No output schema declared.
No examples provided.
mmap_update Record progress on nodes ~123
Update node status/label/evidence. Set in-progress when starting a node (the pane spins), done with evidence when its verification passes, regressed with evidence when a done node breaks. The map is a ledger: report honestly, it never blocks you.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other… |
| updates | array | yes | – |
No output schema declared.
No examples provided.
mmap_view View the current map ~140
Render the current Mellos map as monochrome text — the same picture the split-pane watcher shows live. Use it to check the map state or to show it inline in conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other… |
| zoom | integer | – | zoom ladder: 1 = detail (notes unfold), 0 = standard (default), -1..-3 = scaled down, -4 = overview glyphs |
No output schema declared.
No examples provided.