Scans Dashboard
In the Scans dashboard, you can explore such metrics as the total number of scans (Scans), lines of code (Scanned LOC), the total number of scanned projects (Scanned Projects), the total number of developers and scans for each tool or IDE (Total Scans by Developers), etc.
 |
In the Scans dashboard, you will also find the following charts:
Lines of Code: An overview of the total lines of code across all scanned projects. It helps you understand the scale of the codebase under analysis and track changes over time.
Scanned Projects: The number of scanned projects within the specified timeframe.
Scans Status: This chart provides an overview of the status of your security scans. It categorizes scans into statuses such as Successful, Failed, and Partial. This breakdown helps you quickly assess the outcome of your scanning activities, highlighting areas that require immediate attention and areas where your security measures are effective.
Incremental Scans (SAST): The number of incremental scans performed using the SAST scanner.
Scanner Usage Distribution: A breakdown of the usage of different scanners.
Scanners Used in Combination: This chart visualizes the combinations of scanners used in code-scanning workflows.
IDE Usage Over Time: This chart shows how many unique developers are running scans over time, grouped by the tool they used. Time is shown on the X-axis (usually by week), and the number of developers on the Y-axis. Each bar is split by IDE type, using different colors to help compare usage.
The IDE KPI uses the following data:
Scan origin: Where the scan came from (e.g., VS Code, JetBrains, Eclipse, or Visual Studio).
Initiator: The number of unique developers who triggered the scan.
Scans: The total number of scans started from those tools.
Others: Any scan sources that aren’t among the main IDEs.