dependency-extractor

To extract module dependencies across a multi-language monorepo, this automation reads root build files to identify modules, resolves inter-module references, and classifies modules by type to generate a machine-readable dependency map.

Yes, you can generate an architecture diagram from Maven or Gradle build files. The tool parses root build configurations, verifies imports, and outputs a human-readable MODULE-ARCHITECTURE.md diagram for documentation.

Dependency extraction works with npm workspaces and .NET solutions. It supports these alongside Maven, Gradle, and Python monorepos to detect module boundaries and map inter-module dependencies automatically.

The best way to map codebase structure for change impact assessment is to automate inter-module dependency extraction, producing a machine-readable JSON dependency map that verifies imports and classifies modules by type.

You should regenerate the module dependency map after bootstrapping a project or whenever the module structure changes. This ensures the architecture diagram and dependency map accurately reflect current inter-module references.

Mapping inter-module dependencies generates two output files: a machine-readable .github/module-dependency-map.json for automation and a human-readable .github/MODULE-ARCHITECTURE.md for architecture reference.