vx overview

vx overview gives you a high-level picture of your codebase in one command — total files, total dependency edges, and the top 10 most-depended-on files ranked by how many files would be affected if they changed.

Run vx init in your repository first to build the dependency snapshot before using vx overview.

Command

Terminal

vx overview

Output

overview  |  554 files  |  3541 edges

most depended-on:
  packages/common/src/index                                    ← 218 file(s)
  packages/excalidraw/src/types                                ← 141 file(s)
  packages/excalidraw/src/constants                            ← 112 file(s)
  packages/excalidraw/src/actions/manager                      ← 89 file(s)
  ...

files — total source files indexed in the snapshot
edges — total import relationships tracked across the codebase
most depended-on — the files with the highest number of dependents, ranked descending

When to use vx overview

Orienting to an unfamiliar codebase — run vx overview before exploring. The most-depended-on list immediately tells you which files are load-bearing and which you can experiment in freely.

Before a refactor — the ranked list shows you where a change will cost the most. Files at the top warrant the most caution, test coverage, and review attention.

Onboarding — hand a new engineer the overview output on day one. It replaces 2–3 weeks of mental model building with a concrete, ranked picture of the codebase.

The risk register framing

The most-depended-on list is effectively a risk register for your codebase. packages/common/src/index with 218 dependents is where bugs cost the most — that file warrants senior reviewers, strong test coverage, and careful deprecation planning. vx overview makes that prioritization objective rather than a gut call.

Supported Languages

Go — resolves via go.mod module name
TypeScript / TSX — resolves relative imports and tsconfig.json path aliases
Python — resolves relative imports