Broken Imports & Unused Dependencies Check — Did the Agent Leave Dead References?
DevMeth checks the 48 known AI-code failure patterns — not a penetration test or a security guarantee.
What the issue is
Imports that resolve to files that do not exist, dependencies that nothing ever uses, and config files loading packages that are not installed are dead references: they build locally by luck and break everywhere else.
Why AI tools generate it
Agents refactor by renaming modules and editing only the imports they are looking at, leaving sibling imports pointing at old paths. They also add dependencies speculatively and configure libraries they never install.
How DevMeth detects it
The scan checks every relative import against the actual file tree, cross-references every declared dependency against imports, scripts, and config references, and checks config-file imports against installed packages. No network call and no build is involved.
Your code imports files that don't exist and declares dependencies nothing uses
WHAT WE FOUND
lib/audit.ts — import { buildAuditNote } from "./missing-helper" — no such file
The fix, in three steps
Resolve each broken import to the real module or delete it, remove dependencies nothing uses, and install or uninstall what config files reference. Each fix is driven per location from the report.
Run a free scan and each finding carries a paste-ready fix prompt you can act on.
Maintainability findings ship in the Rescue Report — bundled with the Launch Pack or available on its own.
Try a free scanFAQ
Why does my project work locally if it has broken imports?
Caches and type hints can hide a stale import on the machine that created it. A fresh checkout, a new developer, or a clean CI build hits the missing file immediately.
Is a dependency that nothing imports harmful?
It is dead weight and risk: a larger supply-chain surface, a version conflict waiting to happen, and an install that ships code the app never runs.
Can I just add a stub file to satisfy the check?
No. A stub that re-exports nothing leaves the real problem — code calling a symbol that does not resolve — exactly where it was. Resolve or delete.
DevMeth checks the 48 known AI-code failure patterns — not a penetration test or a security guarantee. A clear result means each known pattern was checked and found clear or not applicable for your app; it is not a guarantee of security.