Security Insights
Risk Score Methodology
🧮 How it's Calculated:
The score uses a Density-Based Scoring algorithm. It weights every issue found (Critical: 25, High: 15, Medium: 7, Low: 3) and normalizes it against the project's size.
This prevents large projects from having artificially high scores just because they have more files. It measures the concentration of risk per 200 lines of code.
⚠️ Interpretation Guide:
- 80 - 100+: Critical Risk - High concentration of vulnerabilities. Immediate remediation required.
- 40 - 79: Warning - Significant security or quality debt. Needs structured cleanup.
- 0 - 39: Stable - Clean codebase with manageable risks. Continue following best practices.
Initialize New Scan
Repository scan results will appear here
Threat Distribution
Audit Registry
Loading historical data...
Security Compliance
Compliance reports and policy mapping are coming soon in v2.1.
System Configuration
Centralized system settings and AI model management.