See how far a change reaches — and why reach, not diff size, is what predicts risk.
Callers of the changed symbols
Everything downstream of those
Interfaces/APIs others rely on
An estimate from structural reach. Skaftor computes blast radius from your actual dependency and ownership graph. Nothing leaves your browser.
Learn the metric: Blast Radius.
A change's blast radius is the full set of components, contracts, services, and teams it can affect — directly or transitively. Measuring it before merge answers 'what could this break?' so review and testing match real risk.
By traversing the dependency and ownership graph from the changed symbols outward: direct callers, transitive dependents, shared contracts, affected services, and owning teams. This estimator approximates that from counts you enter; Skaftor computes it from your actual graph.
No. Lines changed measures size; blast radius measures reach. A one-line change to a widely-used interface can have a large blast radius, while a big diff in an isolated module can have a small one. Reach predicts risk better than size.