-
Notifications
You must be signed in to change notification settings - Fork 0
Home
pfranccino edited this page Jun 15, 2026
·
3 revisions
Reference documentation for tools to analyze, visualize, and measure the health of module dependencies in Android multi-module projects.
All output shown in these pages is real: it was captured by running the CLIs against the fixtures included in the repo (
tests/fixtures/), so it's fully reproducible after cloning.
| Page | Purpose |
|---|---|
| Commands | Reference for all 4 CLIs: flags, generated files, and real output |
| Sanity Metrics | What Ca/Ce/I mean, what the score penalizes, and where it comes from |
| Static vs Dynamic Engine |
--engine static|dynamic|auto: when to use each |
| Configuration |
analyzer_config.json, analyzer.yml, and the coupling detector |
| CI Integration | Failure gates, JSON output, and GitHub Actions |
| How it works | Module detection, dependency extraction, and diagram generation |
| Troubleshooting | Common problems and how to solve them |
pipx install android-gradle-analyzer # from PyPI
pipx install "android-gradle-analyzer[kts]" # + AST parser for .kts| Command | Question it answers |
|---|---|
gradle-analyzer <module> |
How do the submodules of this feature depend on each other? |
gradle-externals <project> <module> |
Who is consuming this module from outside? |
gradle-sanity <module> |
How healthy is this dependency architecture? |
gradle-impact <project> <module> |
What breaks if I change this module? |
See the full reference in Commands.