Know your blast radius
before you release.
Depgraph scans npm, PyPI, or crates.io and maps exactly who depends on your library. Before you ship a breaking change, see the ten most at-risk packages — with plain-English summaries of what breaks and why.
From "I think this is safe" to "I know who breaks"
Three steps. No guesswork.
Point at your package
Paste a package name from npm, PyPI, or crates.io. Depgraph looks up your real published dependents, not just what the registry counts.
We trace the graph
We walk the dependency graph and analyze which downstream packages actually use the API surface you're changing — not just which ones list you in their manifest.
Get your impact report
Ten most at-risk dependents, ranked by severity. Each one gets a plain-English summary: what breaks, which call sites, what a migration would look like.
Built for maintainers who've been burned
You already write the changelogs. Depgraph gives you the evidence to back them.
High-traffic packages
You have thousands of dependents and no way to know which ones will actually break. Depgraph narrows it to the packages that call the code you're changing.
Major version releases
Planning a v2 or a semver-breaking API change? Know the full blast radius before you tag the release — not after the issues pile in over a weekend.
Deprecation notices
Stop writing migration guides based on assumptions. Depgraph surfaces the real call sites so your deprecation notice is backed by actual evidence, not guesswork.
Stop guessing.
Ship with evidence.
Join early access and be first in line when we open the gates.