Limits
What the analysis cannot see, it says it cannot see. This is the list.
- Reachability is static. Reflection, plugin discovery by directory scan, and consumers outside the repository are invisible; that is why
ORPHANis a candidate andwhyexists. - Only Python and JavaScript/TypeScript have analyzers today. Everything else (Go, Rust, Java ...) gets volume and activity.
- JavaScript specifics it cannot see: aliases defined only in a bundler config (
vite.config,webpack.config;@/and~/are guessed),exportswildcard patterns as entry points (list those underkeep), auto-imports (unplugin-auto-import, Nuxt-style component directories outside the frameworks above), arequire()written inside a template literal's${}, and scripts in extensionless hook files such as.husky/pre-commit. - Git activity needs history: a shallow clone truncates it, and a repository with no commits yet reports statuses as
UNKNOWN. A moved file keeps its history when git recognises the move (its default similarity threshold); a file rewritten beyond recognition when moved starts over, and a path re-created after a move is a new file.triageandcheckfollow the same moves, committed or not, as long asgit mvorgit addhas told git about them; a renamed file that was not added is a deletion and an untracked addition. - The HTML explorer's script is exercised against the Python implementation, but the page's sorting and filtering are checked by hand in a browser, not by an automated test.
- The module graph is static imports between Python and JavaScript/TypeScript files. A package that re-exports everything (a busy
__init__.pyorindex.ts) makes the modules importing through it look more tangled than their real call graph, and registries, dependency injection and dynamic loading leave no edge, so a missing dependency is not proof there is none. - A dotted name or path in a string is an edge of kind
string, andimpactfollows it by default. A tool that names files in strings links itself to them: a stringscripts/run.pyin a module is an edge to that file whether or not the module runs it. A bare name that several files share is not resolved, wherever it was found, and the report's caveats list it; the bare__init__.pyand__main__.py(and theif __name__ == "__main__"idiom) make no edge. - A string that names
a.b.calso depends on thea/__init__.pyanda/b/__init__.pyPython runs on the way, markedstringlike the module itself, where an import statement marks thempackage;impact --edges importsleaves both out, andcheckknows that a name which names a module only runs its packages on the way. - Review load counts lines changed, not effort: a generated file that is not excluded, or a mechanical rename of one symbol, weighs as much as careful work. It cannot see who reviewed, and it does not see branches that never reached the history it reads.
- Ownership says who has been changing code, not who is accountable, and git cannot tell who reviewed it. Squash merges credit the person who merged, a person with different names on different machines counts as several, and two people with one name count as one. Work done in another repository or before a history rewrite is invisible. Read it as a prompt to ask, not as an assignment.
- Symbol-level dead code (unused functions inside live files) is out of scope; use a tool like vulture. For multi-language dead-code detection see fossil-mcp; for churn x complexity on JS/TS see fallow.
Source: docs/guide/limits.md, Markdown in the repository; this page is built from it. Edit it on GitHub.