Explore the structure

Follow the connections.

Find what depends on your code. See what your code depends on.

2groups

1connections

2dependencies

MODULE MAPAll arms

Inspect a module ↓

UpstreamDownstreamCycle return

2 groups · 1 connections · drag to panSCROLL to zoom · CLICK to trace · ESC to clear

Every module has a story.

Select a node to trace its connections, or find a module in the explorer.

Keep exploring

From the map to your terminal.

COMPUTED FROM CODE

The pillars1 arms · crowns & evidence

The arms the walk proposes. Each crown is the unit that orchestrates its arm.

  zod · the pillars   0 layers · 0 nodes · 0 edges · 1 unconnected · [LR]

   
   
   
  unconnected (1):
┌─────┐  
│ ZOD │  
└─────┘

Arm	Crown	Units	Evidence
ZOD	zod._configs	7

The package ring0 connected packages

Minted beside zod: none.

Not carried: arktype, benchmark, chalk, console_table_printer, effect, esbuild, execa, mitata, recheck, rollup, rollup__plugin_commonjs, rollup__plugin_node_resolve, rollup__plugin_typescript, rollup_plugin_bundle_size, rollup_plugin_filesize, seriousme__openapi_schema_validator, sinclair__typebox, tinybench, typia, valibot, vitest, web_std__file, yup, zod3, zod__mini.

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 zod._configs --tenant /site/.work/colinhacks/zod/.graphy/tenant.json --tenant-id zodif zod._configs changes, what breaks
/usr/local/bin/graphy descend zod._configs --tenant /site/.work/colinhacks/zod/.graphy/tenant.json --tenant-id zod --depth 3what zod._configs reaches, across packages
/usr/local/bin/graphy draw --tenant /site/.work/colinhacks/zod/.graphy/tenant.json --tenant-id zod --symbol zod._configs --radius 2 --lrthe neighbourhood, drawn

Make your own atlasOne command · no model

pip install graphyos
cd <repo> && graphy eat . && graphy showcase .

https://github.com/colinhacks/zod.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; 1 below that floor.