Code Health & Dead-Code Detection

The Code Health tab surfaces signals that fall outside traditional SAST results — including dead code, duplicate code clusters, and maintenance concerns. To access it:

1. Open a completed scan from the Scans tab.
2. Click the Code Health tab (HeartPulse icon) in the scan detail page.
3. A table of code-health signals appears, each with a signal type, severity, affected file, and description.
4. Filter by signal type (dead code, duplicates, etc.) or severity (Critical, High, Medium, Low, Info).
5. Search by keyword or file path to find specific signals.
6. Click any signal row to open a detail drawer on the right showing the full description, affected lines, and recommended action.

What Dead-Code Signals Detect

1. Unused functions — functions that are defined but never called anywhere in the codebase.
2. Unreachable code paths — branches or blocks that can never execute due to control flow.
3. Orphan files — files that are never imported or referenced by other modules.
4. Duplicate clusters — groups of substantially similar code blocks across different files, shown with a similarity score.

Removing dead code reduces attack surface (stale code may contain unpatched vulnerabilities), lowers maintenance overhead, and improves clarity for active development.