How Tangled Is Your Codebase, Really?
Having more modules isn't a problem by itself, but once dependencies between modules pile up, changing one thing starts breaking something unexpected far more often. This calculator combines two metrics common in software engineering β average dependencies per module and dependency density (the ratio of actual connections to all possible connections) β into a single complexity score.
Just enter your total module count and dependency edge count, and it shows the average dependency count, density, an overall complexity score, and a maintenance difficulty rating. A high score is worth treating as a signal to remove circular dependencies or extract shared functionality into a separate interface to cut direct references. For more reliable numbers, feed in values extracted with a dependency analysis tool like madge or dependency-cruiser instead of estimates.
Frequently Asked Questions
It's the ratio of actual dependency edges to the maximum possible connections. Higher density means modules are more tightly entangled, widening the blast radius of any change.
Eliminate circular dependencies, extract shared functionality into an interface to cut direct references, and draw clearer module boundaries.