What problem does it solve?
Codebases often become hard to evolve due to hidden dependencies, change impact uncertainty, and tangled health metrics. Impact Flow provides a structured way to understand how modules depend on each other, how changes propagate, and where technical debt lurks.
Core Features & Use Cases
- Dependency Graph: visualize imports and module relationships across a project.
- Blast Radius: estimate the ripple effects of a change and identify high-risk areas.
- Health Score: compute a unified view of code health with actionable metrics.
- Flow Tracing: trace execution paths to reveal data flow and call chains.
- Dead Code Detection: surface exports that are unused or risky to modify.
- Comprehensive Analysis: run integrated checks to generate a full report.
- Use Case: Before refactoring the auth module, run impact-flow to map dependencies and identify affected tests.
Quick Start
Run health analysis at the repository root:
impact-flow health .
Then generate a dependency graph:
impact-flow dependencies .
Finally review a flow trace:
impact-flow trace <entry-point-function>