ModuleGraphMetrics
Everything Aalekh knows about one module's position in the dependency graph.
Parameters
Module Gradle path.
Modules that directly depend on this one.
Modules this one directly depends on.
fanOut / (fanIn + fanOut) - 0 stable, 1 unstable.
Modules reachable by following dependencies. Also the module's comprehension cost: how much of the project you must hold in your head to understand it.
Modules that transitively depend on this one - what a breaking change here forces to rebuild, retest, and review.
blastRadius as a share of the project, in [0, 100].
PageRank over the dependency graph, normalised so the mean module scores 1.0. Unlike raw fan-in it weighs who depends on you: being depended on by the app matters more than being depended on by a leaf.
Share of shortest dependency paths that run through this module, in [0, 1]. High betweenness marks a choke point - a module most of the project's structure routes through.
Shortest hop count from the nearest entry point, or -1 when unreachable from any of them. The natural reading order for someone new to the codebase.
Share of this module's outgoing production edges declared api, in [0, 1] - how much of what it depends on it re-exports onto its own consumers.
True when removing this module would split the project into disconnected pieces. A structural bottleneck rather than merely a busy one.
True when nothing depends on this module - a place execution starts.
True when this module depends on nothing - the bottom of the graph.