Legacy Reports Summary tab
Last updated
Last updated
More information
Snyk privacy policy© 2024 Snyk Limited | All product and company names and logos are trademarks of their respective owners.
The main dashboard of the Reports area displays a birds-eye view of all of the issues (vulnerabilities and licenses) found across all of your projects, presenting data for these specific areas:
Security issues
License issues
Your overall project activity—a summary of all of your projects, tests and issues
Data in each tab appears based on the filters you've applied from the top of the Reports area, as well as the Group or Organization that you're viewing from.
To quickly view additional data for a specific period in time, hover over the relevant graph and check out the pop-up.
The following table describes the different parts of the Summary area:
Element | Description |
Security issues | The number of vulnerabilities grouped by severity (Critical, High, Medium or Low), including how many of them Snyk identifies as auto fixable. Click a number to navigate to the Issues tab, filtered to show vulnerabilities for the selected severity only. |
License issues | Sum total of license issues broken down by severity. All statistics in the License issue summary area are linked. Click a number in order to navigate to the Issues tab of the Reports area, filtered to the specific group of license issues. For example, clicking the 28 in the License issues medium severity box navigates to the Issues tab, filtered to those 28 medium severity license issues only. Values:
|
Issues over time | Shows the history of vulnerabilities in your Organization. This shows the number of overall vulnerabilities, and the number of projects being scanned (the dotted line in the graph). |
Exposure window | The elapsed time from when an issue was identified and until it was resolved. |
For the Activity area, the following are the parameters and their descriptions:
Value | Description |
Tests run | Number of tests run. By default, Snyk scans most Projects daily, so an Organization with 100 projects would generate 9,000 scans over 90 days. |
Projects | Number of projects |
New issues | Number of times an issue was introduced in the time period (includes reintroduced issues and deleted projects) |
Fixed issues | Number of fixes applied in the time period (including reintroduced issues and deleted projects) |
Tests preventing issues | Number of occasions when but Snyk scans of a proposed change identified potential issues, so helping prevent you introducing new vulnerabilities to your code. This occurs when your team have incorporated a pipeline or a merge scan (such as GitHub actions or PR checks) that exceed the Snyk scan thresholds. For example, if the number of Critical vulnerabilities in the change exceed the limit. |
Ignored issues | The total number of the issues found, but ignored, as well as the total number of ignored issues that have a fix available. These are issues not counted in any of the other totals in this Summary area. Click the number in the Ignored issues box to jump to the Issues tab, filtered to those ignored issues only. Clicking on the fixable number from the same box navigates to the Issues tab, filtered to those fixable, yet ignored, issues only. Note: After you ignore an issue, it may take up to one hour before synchronizing with the data on the Summary tab of the Reports. |
If you have lots of Projects files to manage and organise in your Organization, you can use filters to focus on specific Projects, or specific types of vulnerability:
For example, if your Organization represents your development team, and you want to focus on (say) front-end work in the next Sprint, click the Projects dropdown and select a subset of the front-end Projects to scan, allowing you to focus on fixing vulnerabilities in that area.
