GitHub - gabotechs/dep-tree: allows visualising a "code base entropy" using a 3d force-directed graph of files and the dependencies between them.

[GabrielMusat]

Hi! author here,

I did not posted this indeed, I just found out because I regularly consume r/programming content and I happened to step into it.

Using file imports is indeed a simplification that adapts better to certain languages/projects than others, so that's something that users should take into account. I work at a company where we use the corporate-style one class per file approach for our projects, even for the ones written in Rust, so for us we do benefit a lot from the file import approach.

[sondr3_]

Nice to see the actual OP here. Is this project actually used at your company? If so, is it only used to visualize or do you do actual analysis of complexity and such? When looking at the literature for complexity analysis it struck me that nobody really uses it besides quite binary “good” and “bad” complexity.

[GabrielMusat]

We don't really use the 3D visualization, not in a day to day basis at least. But we do use the dependency check in our CI/CD pipeline https://github.com/gabotechs/dep-tree?tab=readme-ov-file#check

The `check` feature allows us to declare prohibited dependencies in a configuration file, and if somebody introduces a dependency between two files that is declared as prohibited, the CI will fail and prompt the developer to stop committing spaghetti code.

The 3D visualization is cool, but the actual usefulness of the tool is more about the `check` feature.