GitHub codebase visualization tools
ToolsComments
Regarding those missed imports, I am curious if the tool attempts to resolve paths using a specific build system configuration. Does it parse the tsconfig.json or package.json to handle aliased paths?
The "no installation" claim reminds me of a similar project from a few years back. It hit a hard wall with browser memory limits once the repository exceeded a few thousand files.
Who actually cares about installation anymore? Zero friction is just a marketing term for a tool that isn't powerful enough to require a setup process.
The documentation notes these tools rely on the GitHub API's search endpoint for dependency discovery. This means they are constrained by API rate limits and GitHub's internal indexing rather than performing a full AST traversal.
That API limitation is why these usually fail on the old monoliths we manage. If the tool misses a deep import because of a rate limit, the resulting map is misleading.