Overview of the project: languages, module count, Python packages, guessed entry points (pyproject scripts, main.py, package.json bin/main/exports), import-cycle count, unresolved/dynamic imports, and syntax-error files. Start here.

Who imports this file? Transitive importers grouped by depth, with the import line, imported names, and flags (type-only / lazy / conditional). path_or_module is a project-relative path (src/app/util.py, packages/ui/src/Button.tsx), an extensionless JS path, or a dotted Python module (app.util). Depth 1 = direct importers only.

What does this file import from inside the project (transitively up to depth)? Also lists this file's UNRESOLVED and DYNAMIC imports explicitly.

Blast radius of changing a file (or one symbol in it): direct and transitive dependents, the tests that reach it through imports (run these), entry points affected, and a LOW/MEDIUM/HIGH risk summary with reasons. With symbol, direct users are narrowed to files that import or access that name (following re-exports); the rest is an upper bound.

Import cycles: strongly connected components (Tarjan), each with its shortest cycle spelled out file by file, and whether the cycle is softened by lazy/type-only imports.

Dead-code candidates (files nothing imports that are not entry points, tests, init.py or configs - with caveats) and the most depended-on files (direct importers / transitive dependents).

Who uses symbol from module? Best effort and labeled as such: from-imports, named imports, attribute access on the module alias (mod.name), wildcard imports, and re-export chains (init.py, all, export {x} from). getattr()/dynamic use is invisible.