What Is Blast Radius in Code?
In software, the blast radius of a change is the full set of code that the change can affect — every file, function, API route and page that depends on what you are about to modify, directly or through a chain of other dependencies.
Direct and transitive dependents
A file's direct dependents are the ones that import it. Its transitive dependents are everything that imports those, and so on outward. The blast radius is all of them together, because a change to a shared function can surface as a bug several imports away from where you edited.
The term is borrowed from incident response and infrastructure, where it describes how far the damage from a failure spreads. In code it describes how far the effect of an edit spreads.
Why guessing is not enough
A guess based on folder structure or file names misses the paths that cross module boundaries. The reliable answer comes from the real import and call graph: start at the symbol you are changing and walk the dependency edges outward.
Knowing the blast radius before you ship lets a reviewer see the scope of a change before they see the diff, and puts the untested dependents — where regressions hide — at the top of the list.
Common questions
What is blast radius in software?
It is the complete set of code a change can affect: every file, function, API route and page that depends on the code being modified, directly or through a chain of dependencies.
How do you calculate the blast radius of a code change?
Start at the symbol or file you are changing and walk the dependency graph outward, following every import and call edge, until you have every file, route and page that transitively depends on it.
Is blast radius the same as change impact analysis?
No. Blast radius is the set of affected code. Change impact analysis is the practice of working that set out before you make the change.
Related
- Change impact analysis tool — Map the exact blast radius of any code change before you ship. Plain-English change impact analysis, traced through your real dependency graph. Try it free.
- Code dependency mapping — Visualize your codebase architecture as a live dependency graph, built automatically from every import and route, with high-blast-radius hubs highlighted.
- Change impact analysis — glossary
- Dependency graph — glossary
See it in your own codebase.
Analyze my codebase →No credit card required · Free tier available