This looks potentially useful.

When I tried this on a Rust project it said to run "codegraph cluster-only <path>". but I had to first uv pip install codegraph, and then codegraph -h did not have any cluster-only (it had -o and --object-only). (codegraph cluster-only <path> fails with an error.) The -o output was hard to understand.

Maybe a web-based version that takes a github repo URL and analyzes that might be a better way to demo this? After trying that a user could install locally and use with an LLM for more in-depth results.

I wanted to try this on a small, simple Rust project before trying it on a large, complex Rust project. My Rust projects tend to be multi-component (each "component" is a multi-crate workspace). How large a project have you tested this on? How did you test this on all the supported languages? How can I add a language that you do not yet support?

How do you calculate tech debt? Every code scanner usually has a unique definition based on what they can measure. I'm interested to know what yours is and how you chose it.