Code Map
See how a codebase fits together before you read it.
pyrovue reads every import in a repository and draws the result: which files form the UI, the API and the data layer, which groups of files work together, the files everything depends on, and the import cycles. No AI is involved, and the map stays after the box goes to sleep.
What the map shows
Four views of the same import graph.
- LayersUI · routes · API · services · data · …
- Each file is sorted into a layer from its framework's conventions, its name and folder, and what it contains (routes registered, JSX, SQL), so you see how the app is built.
- ClustersLouvain on the import graph
- Files that import each other closely are grouped, and each group is named after its main folder. Clusters are the modules a team would draw on a whiteboard.
- HotspotsPageRank
- The files the rest of the code depends on most, ranked the way search engines rank pages. Start reading there.
- Import cyclesup to 25 listed
- Files that import each other in a loop, found as strongly connected components, so you can see what to untangle first.
- Entry pointswhere execution starts
- The files a run starts from, such as servers, pages and scripts, so you know where to begin reading.
Languages
Sixteen languages, resolved properly.
Imports are resolved the way the language does it, so @/components/Button and from .models import User point at real files.
- JavaScript and TypeScript
- Including Vue, Svelte and Astro files,
tsconfigpaths andbaseUrl,@/and~/aliases, index files and workspace packages. - Python
- Packages, relative imports and
src/layouts. The standard library is left out so the map shows your code. - Go and Rust
- Go modules, and Rust
modanduse. - Ruby, PHP, Java, Kotlin, C# and C/C++
- PSR-4 namespaces, JVM packages and C includes.
Numbers
Fast, and the same every time.
A map covers up to 4,000 source files and 20,000 resolved imports, and takes about two seconds for the largest. Because it's built from the code alone, with no model calls, running it twice gives the same map.
The map has limits worth knowing: it reads imports with patterns rather than a full parser, so imports built at runtime (a path assembled from a variable, a plugin loaded by name) are missed.
The tour
A guided walk through the code.
Next to the map, every box gets a tour: a short series of stops through the files that matter, each pinned to real lines. When Claude sets up a repo it writes the tour from what it learned, and every stop is checked against the actual file. Without Claude, the tour is built from the map.
Questions
Asked often.
Run the repo you bookmarked and never tried.
Hobby is free and needs no card. Paste a link and your first box is up in about a minute.