Use case

Dependency Graphs without the hairball

Visualize npm, Cargo, Go modules, microservice topologies, and architecture maps. Find cycles and critical paths in a few seconds, not a few minutes.

The problem

Real package graphs grow circular fast. Visualizing without highlighting the cycles is just noise.

Build engineers want to see the longest chain immediately, not after a manual zoom-and-trace.

A monorepo dependency graph easily exceeds 5,000 edges. Most libraries become a hairball.

Show only direct deps, transitive deps, dev-deps, peer-deps — without re-rendering the whole tree.

Pick the right algorithm for your graph shape. Switch with a single property change.

Combine highlight() with your own pathfinder to spotlight the longest chain.

Untangle dense edge sets in a monorepo dep graph.

Toggle prod / dev / peer / optional dependencies with a flag — no re-mount.

Start with the root package and expand neighbors on demand. Keeps initial render fast.

Find a package by name and jump to it; the minimap helps users orient.

Live demo with cycle detection, critical-path highlight, and filtering.