Dead Exports Check — Is Your Codebase Carrying Unused Exports?
DevMeth checks the 48 known AI-code failure patterns — not a penetration test or a security guarantee.
What the issue is
Exported functions, classes, and constants that no other file in the project ever references are dead weight. They increase the surface people must read, and they are typically the leftovers of a refactor that was never finished.
Why AI tools generate it
AI code assistants build incrementally and rarely clean up the version they replaced. A botched refactor leaves the old exported helper in place, exporting it into a void because nothing imports it anymore.
How DevMeth detects it
A project-wide scan indexes every identifier and flags exported symbols whose name appears in their own file and nowhere else. Framework entry-point files are exempt, because the framework imports those by path.
Exported functions and classes that nothing ever imports — dead code from an unfinished refactor
WHAT WE FOUND
lib/slugify.ts — export function slugify() — referenced nowhere else
The fix, in three steps
Verify no other file references the symbol, then either delete it or strip the export keyword to make it a private helper. The report's paste-ready prompt drives this per location.
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
Is every unused export worth removing?
Yes — dead exports survive only because nothing breaks, and they mislead future readers into treating them as part of your public surface. Removing them is one of the fastest maintainability wins.
Does this scan risk flagging framework entry points?
No. Framework convention files like pages, routes, layouts, and middleware are imported by path rather than by symbol, so the scan exempts them by design.
What if my search for a symbol finds nothing but I still need it?
Then it is not reachable by any code path. Either re-wire the reference or delete the symbol — a symbol nothing can trigger might as well not exist.
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.