techdebt

Scanning for technical debt involves analyzing code structure to detect duplication, dead code, and type safety issues. The tool then provides a prioritized action plan with actionable cleanup recommendations to improve maintainability.

To find dead code, the scanner flags unused imports, exports, and files by analyzing your codebase structure. It identifies these unused elements and suggests removal to keep the project clean and efficient.

Code duplication detection works by scanning the codebase to identify repeated code blocks. Once found, it suggests extraction opportunities to consolidate the repeated logic into shared, maintainable components.

Yes, you can detect type safety issues like `any` types and missing annotations. The analysis scans the codebase to flag these inconsistencies and provides recommendations to enforce stricter type safety.

You should run a technical debt scan after a development sprint. This timing allows you to get a report on areas needing refactoring, ensuring the codebase remains clean and efficient before starting new work.

Yes, the scanner identifies performance anti-patterns alongside dead code and duplication. It analyzes the codebase structure to detect these inefficiencies and suggests refactoring opportunities based on established patterns and project context.