Explore the structure
Follow the connections.
Find what depends on your code. See what your code depends on.
Select a node to trace its connections, or find a module in the explorer.
Keep exploring
From the map to your terminal.
The pillars6 arms · crowns & evidence
The arms the walk proposes. Each crown is the unit that orchestrates its arm.
hono · the pillars 5 layers · 7 nodes · 15 edges · 0 unconnected · [LR]
┌───────────────────┐ ┌────────────────────────────────────────────────────────────────────────────┐ ┌──────────────────┐
│ ADAPTER (45→ ·→0) ├─┤ └┌┌┌┌┌▶│ UTILS (8→ ·→249) │
└───────────────────┘ ├─────────────────────────────────────────────┐┌──────────────────────────────┘││││ └──────────────────┘
│ ││ ││││
┌──────────────────┐ │ ┌───────────────┐┌─────────────────────────╪┘ ┌────────────────────────┐ ││││
│ PRESET (12→ ·→0) ├──╪┐▶│ EDGE (5→ ·→3) ├┤ └┌┌┌▶│ MIDDLEWARE (137→ ·→15) ├──╪┘││
└──────────────────┘ ││ └───────────────┘├──────────────────────────┘││ └────────────────────────┘ │ ││
││ │ ││ │ ││
┌────────────────────┐└╪──────────────────╪┐ ┌───────────────────┐ ├╪─────────────────────────────┘ ││
│ VALIDATOR (8→ ·→0) ├┐│ └╪┌┌▶│ HELPER (91→ ·→39) ├──┘│ ││
└────────────────────┘│├────────────────────┘│ └───────────────────┘┌──╪───────────────────────────────┘│
││ │ │ │ │
│└─────────────────────╪──────────────────────┘┌─╪────────────────────────────────┘
│ │ │ │
├──────────────────────╪───────────────────────╪─┘
│ │ │
├───────────────────┌──╪───────────────────────┘
│ │
└───────────────────┘
| Arm | Crown | Units | Evidence |
|---|---|---|---|
| MIDDLEWARE | hono.middleware | 4 | crown — fan-out at least half the leader's (111) |
| HELPER | hono.helper | 4 | crown — fan-out at least half the leader's (111) |
| ADAPTER | hono.adapter | 1 | crown — stands alone: no arm orchestrates it, and the most it spends on one arm is 14 of 45 (HELPER), under 0.33 |
| PRESET | hono.preset | 1 | crown — stands alone: no arm orchestrates it, and the most it spends on one arm is 2 of 12 (HELPER), under 0.33 |
| VALIDATOR | hono.validator | 1 | crown — stands alone: no arm orchestrates it, and the most it spends on one arm is 1 of 8 (HELPER), under 0.33 |
| UTILS | hono.utils | 5 | the floor's crown — the greatest fan-in (142) no arm owns (MIDDLEWARE 66, HELPER 48, ADAPTER 6, VALIDATOR 3) |
Compiled arms live at /site/.work/honojs/hono/.graphy/GRAPH.md. Open one arm; blast its crown.
The package ring0 connected packages
Minted beside hono: none.
Not carried: esbuild, jsdom, msw, vitest, zod.
Add your modelMCP configuration
Paste this into the repo's .mcp.json (Claude Code) or your client's MCP settings. The client can start anywhere in the repo. Any model; the walk is graphy's.
{
"mcpServers": {
"graphy": {
"command": "/usr/local/bin/graphy",
"args": [
"mcp",
"--repo",
"."
]
}
}
}Ask the codebaseThree starting points
/usr/local/bin/graphy blast hono.middleware --tenant /site/.work/honojs/hono/.graphy/tenant.json --tenant-id honoif hono.middleware changes, what breaks/usr/local/bin/graphy descend hono.utils --tenant /site/.work/honojs/hono/.graphy/tenant.json --tenant-id hono --depth 3what hono.utils reaches, across packages/usr/local/bin/graphy draw --tenant /site/.work/honojs/hono/.graphy/tenant.json --tenant-id hono --symbol hono.middleware --radius 2 --lrthe neighbourhood, drawn
Make your own atlasOne command · no model
pip install graphyos cd <repo> && graphy eat . && graphy showcase .
https://github.com/honojs/hono.git
Every edge comes from code structure, a wormhole between packages, or a label resolved through the code's own scope. The module map shows cross-group connections with at least 2 dependencies; 30 below that floor.