Explore the structure

Follow the connections.

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

16groups

37connections

202dependencies

MODULE MAPAll arms

Inspect a module ↓

UpstreamDownstreamCycle return

16 groups · 37 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 pillars4 arms · crowns & evidence

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

  typer · the pillars   5 layers · 5 nodes · 10 edges · 0 unconnected · [LR]

┌───────────────┐┌────────────────────┐  ┌───────────────────┐┌─────────────────────┐    ┌─────────────────┐  
│ CLI (27→ ·→1) ├┤                    └┌◀│ CLICK (18→ ·→104) ├┤                     └╪┌┌◀│ MAIN (61→ ·→15) │  
└───────────────┘├────────────────────┐│ └───────────────────┘│   ┌────────────────┐ │││ └─────────────────┘  
                 │                    ││                      └╪┌▶│ EDGE (8→ ·→11) ├─╪╪┘                      
                 │ ┌─────────────────┐└╪───────────────────────┘│ └────────────────┘ ││                       
                 ├▶│ CORE (42→ ·→25) ├─┤                        │                    ││                       
                 │ └─────────────────┘ ├──────────────────────┌─╪────────────────────╪┘                       
                 │                     │                      │                      │                        
                 └────────────────────┐└──────────────────────┘┌─────────────────────┘                        
                                      │                        │                                              
                                      └────────────────────────┘

Arm	Crown	Units	Evidence
MAIN	typer.main	9	crown — fan-out at least half the leader's (56)
CORE	typer.core	1	crown — fan-out at least half the leader's (56)
CLI	typer.cli	1	crown — stands alone: no arm orchestrates it, and the most it spends on one arm is 7 of 27 (CORE), under 0.33
CLICK	typer._click	4	the floor's crown — the greatest fan-in (78) no arm owns (MAIN 33, CORE 26, CLI 8)

Compiled arms live at /site/.work/fastapi/typer/.graphy/GRAPH.md. Open one arm; blast its crown.

The package ring0 connected packages

Minted beside typer: none.

Not carried: _typeshed, annotated_doc, colorama, rich, shellingham, typing_extensions.

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

Make your own atlasOne command · no model

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

https://github.com/fastapi/typer.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; 27 below that floor.