Monitor Code Health
The Code Health dashboard gives you a real-time view of your codebase’s quality, maintainability, and technical debt. This guide shows you how to read the dashboard, interpret trends, and use the AI-powered actions to improve your code.
Opening the Dashboard
Understanding the Metrics
Quality Score (0-100)
Your composite quality score combines all dimensions into a single number:
| Range | Grade | Interpretation |
|---|---|---|
| 90-100 | Excellent | Minimal issues. Well-maintained codebase |
| 70-89 | Good | Some improvements needed but generally healthy |
| 50-69 | Fair | Significant issues present. Prioritize remediation |
| Below 50 | Poor | Immediate attention needed. Major quality risks |
Rating System (A-E)
Three independent ratings evaluate different aspects:
| Rating | Reliability (Bugs) | Security (Vulnerabilities) | Maintainability (Code Smells) |
|---|---|---|---|
| A | No significant bugs | No vulnerabilities | Clean, maintainable code |
| B | Minor bugs | Low-risk vulnerabilities | Minor code smells |
| C | Moderate bugs | Moderate vulnerabilities | Noticeable code quality issues |
| D | Significant bugs | High-risk vulnerabilities | Substantial maintenance burden |
| E | Critical bugs | Critical vulnerabilities | Severe maintainability issues |
Detailed Metrics
| Metric | What It Measures | Ideal Range |
|---|---|---|
| Complexity Score | Average cyclomatic complexity across functions (0-100) | Below 40 |
| Maintainability Index | Industry-standard readability and maintainability metric (0-100) | Above 60 |
| Dead Code Count | Number of unused functions, variables, and imports detected | 0 |
| Duplicate Blocks | Count of copy-paste code block pairs found | Below 10 |
Reading the Technical Debt Trend
The trend chart shows your quality score evolution over the last 10 scans. Look for:
- Upward trend — Quality is improving. Your remediation efforts are working
- Flat line — Stable but not improving. Consider allocating time for tech debt
- Downward trend — Quality is degrading. New code may be introducing issues faster than they’re fixed
- Sudden drops — A specific change introduced significant issues. Check the scan that caused the dip
Using AI-Powered Actions
The Code Health dashboard provides four AI-powered actions for any finding:
Using AI Fix
- Click on any issue in the Code Smells, Bugs, or Vulnerabilities list
- Click Fix with AI
- Review the generated fix — it shows the original code and the corrected version
- Copy the fix and apply it to your codebase
- Trigger a new scan to verify the issue is resolved
Code Smell Categories
The dashboard breaks down code smells into categories:
| Category | Examples |
|---|---|
| Complexity | Functions with high cyclomatic complexity, deeply nested logic |
| Dead Code | Unused functions, unreachable branches, unused imports |
| Duplication | Copy-paste code blocks, repeated logic across files |
| Naming | Non-descriptive variable names, inconsistent naming conventions |
| Security | Weak cryptographic patterns, insecure defaults |
| Style | Formatting issues, inconsistent patterns |
High Risk Files
The dashboard highlights files with the most concentrated issues. These are your best candidates for refactoring — fixing one high-risk file can significantly improve your overall score.
Prioritize files that are:
- Frequently modified (high change velocity + high risk = high exposure)
- In critical paths (authentication, payment, data access)
- Shared across features (utilities, base classes)
Monitoring Workflow
For ongoing quality monitoring, follow this weekly routine:
Related Guides
- Configure Code Quality Tools — Adjust what the quality scanners report
- Set Up Quality Gates — Define minimum standards for your quality score
- Triage Vulnerabilities — Handle security findings systematically