wiringmap

See how your code is wired. wiringmap turns any Python project into an interactive map: what every file uses, what uses it, and what breaks if you change it. It runs offline, produces one HTML file, and needs no AI.

_{Shown above: fastapi/full-stack-fastapi-template.}

Why

An AI agent wrote most of your code. It works, but you have never read most of it, and now you need to change something. Which file does what? What calls this function? What breaks if you touch it?

wiringmap answers those questions in seconds, and your code never leaves your machine.

Try it

You need uv. Then, inside any Python project:

uvx --from git+https://github.com/Burnaviour/wiringmap wiringmap build . --open

This writes .wiringmap/report.html and opens it in your browser. The .wiringmap/ folder ignores itself, so it is never committed by accident.

What you get

• A map of the whole project. Files are boxes inside their folders, and arrows show imports. Switch to Calls to see which files call into which; thicker arrows mean more calls. Large projects start with folders closed (double-click to open one), and tests, docs and migrations stay closed so you see the application first.
• Click a file to see what it uses (indigo), what uses it (amber), its docstring, and the classes and functions inside it.
• Click a function to see what it calls and what calls it. Each link says how it was found: resolved from names and imports, inferred from type hints, or guessed from a unique method name.
• "Start reading here" lists where the program starts: commands, scripts, and web routes with their method and path (POST /login/access-token).
• Search every file, class and function with /, and read the source next to the map.
• Big projects work too. pandas (1,411 files) scans in under 8 seconds, and its report opens in under one.

Private by design

• wiringmap reads your code; it never runs it.
• Nothing is uploaded. The report is one self-contained file that makes no network requests, so you can open it offline or send it to a teammate.
• --no-source leaves your source code out of the report, keeping only its structure.

Options

wiringmap scan . writes only the data, graph.json: every file, class and function plus the imports, calls, inheritance and decorators between them. Its format is documented in docs/graph-schema.md, so you can build your own tools on it.

Roadmap

• Code graph for Python, with call links that say how sure they are
• Interactive offline map with search and source view
• Flow view: follow a command or web request step by step through the code
• Framework wiring: FastAPI Depends, callbacks and overridden methods as links
• Plain-English explanations of files, folders and flows from a local model (Ollama), optional
• JavaScript and TypeScript

Contributing

Bug reports and ideas are welcome: please open an issue. To work on the code, see CONTRIBUTING.md and how wiringmap works.

If wiringmap helps you, a ⭐ helps other people find it.

License

MIT. Reports bundle Preact (MIT), htm (Apache-2.0), Cytoscape.js and cytoscape-fcose (MIT); see their licenses.