Technical debt scanning that runs where your code lives.

The problem this page helps clarify

The useful question is where Technical debt scanning changes the review loop: what enters the scan, who acts on a finding, and which evidence moves forward. Duplicate logic, dead-code signals, dependency cycles, oversized modules, and review-risk trends.

• Audience: Maintainers deciding which structural debt should be fixed before it compounds.
• Focus: Duplicate logic, dead-code signals, dependency cycles, oversized modules, and review-risk trends.
• Review question: What does Technical debt scanning cover in practice?

Coverage and concrete signals

For Technical debt scanning, inspect the concrete scope below instead of relying on a category label. Findings that name the affected structure, explain the review cost, and produce portable reports.

• Focus: Duplicate logic, dead-code signals, dependency cycles, oversized modules, and review-risk trends.
• Workflow: Workflow: duplicate code · dead code · dependency cycles · oversized files
• Coverage and concrete signals: duplicate code, dead code, dependency cycles, oversized files

From local signal to shared gate.

Technical debt scanning: Use the smallest workflow that proves value. Each later step should reuse evidence the team already understands. Duplicate logic, dead-code signals, dependency cycles, oversized modules, and review-risk trends.

Copyradar scan . --quick
radar scan . --format sarif --fail-on high

Evidence to inspect before you trust the result.

Technical debt scanning: A useful result must be explainable to a developer and portable to the next review surface. Inspect the concrete evidence below before changing team policy. Findings that name the affected structure, explain the review cost, and produce portable reports.

• Workflow: duplicate code · dead code · dependency cycles · oversized files
• Exact file location, rule context, severity, confidence, and remediation guidance.
• Terminal output, SARIF, JSON, or HTML artifacts generated from the same finding set.
• Source stays in the workspace or CI runner where the scan executes.

Good fit and limits

Use Technical debt scanning when Maintainers deciding which structural debt should be fixed before it compounds. Keep the boundary explicit: Debt detection is a prioritization aid; teams still need ownership, context, and a deliberate refactor plan.

Run the local proof before adopting a shared gate.

• Good fit: Maintainers deciding which structural debt should be fixed before it compounds.
• Not a fit / do not overreach: Debt detection is a prioritization aid; teams still need ownership, context, and a deliberate refactor plan.

Questions to verify before rollout

These questions keep the decision tied to observable evidence rather than a broad product promise.