# Source: https://docs.snyk.io/manage-risk/reporting/legacy-reports/legacy-reports-summary-tab.md

# Legacy reports summary tab

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

<figure><img src="https://2533899886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdwVZ6HOZriajCf5nXH%2Fuploads%2Fgit-blob-7f8333638d92001f8580ef7644c46b32c867a308%2FScreenshot%202022-08-11%20at%2009.42.46.png?alt=media" alt="Report Summary tab"><figcaption><p>Report Summary tab</p></figcaption></figure>

{% hint style="info" %}
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.
{% endhint %}

To quickly view additional data for a specific period in time, hover over the relevant graph and check out the pop-up.

## **Summary tab elements**

The following table describes the different parts of the **Summary** area:

| Security issues  | <p>The number of vulnerabilities grouped by severity (Critical, High, Medium or Low), including how many of them Snyk identifies as auto fixable.</p><p>Click a number to navigate to the <a href="legacy-reports-issues-tab"><strong>Issues</strong> tab</a>, filtered to show vulnerabilities for the selected severity only.</p>                                                                                                                                                                                                                                                                            |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| License issues   | <p>Sum total of license issues broken down by severity.</p><p>All statistics in the <strong>License issue summary</strong> area are linked. Click a number in order to navigate to the <strong>Issues</strong> tab of the <strong>Reports</strong> area, filtered to the specific group of license issues.</p><p>For example, clicking the 28 in the <strong>License</strong> issues medium severity box navigates to the <strong>Issues</strong> tab, filtered to those 28 medium severity license issues only.</p><p>Values:</p><ul><li>High severity</li><li>Medium severity</li><li>Low severity</li></ul> |
| Issues over time | <p>Shows the history of vulnerabilities in your Organization.</p><p><br>This shows the number of overall vulnerabilities, and the number of projects being scanned (the dotted line in the graph).</p>                                                                                                                                                                                                                                                                                                                                                                                                         |
| Exposure window  | The elapsed time from when an issue was identified and until it was resolved.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |

## Activity

<figure><img src="https://2533899886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdwVZ6HOZriajCf5nXH%2Fuploads%2Fgit-blob-dfb0d03987458ff411f4af8a9d91ff9e9399c0da%2Fimage.png?alt=media" alt="Activity section"><figcaption><p>Activity section</p></figcaption></figure>

For the **Activity** area, the following are the parameters and their descriptions:

| 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 | <p>Number of occasions when but Snyk scans of a proposed change identified potential issues, so helping prevent you introducing new vulnerabilities to your code.<br>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.<br>For example, if the number of Critical vulnerabilities in the change exceed the limit.</p>                                                                                                                                                                                                                                                                                  |
| Ignored issues          | <p>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 <strong>Summary</strong> area.</p><p>Click the number in the <strong>Ignored</strong> issues box to jump to the <strong>Issues</strong> tab, filtered to those ignored issues only. Clicking on the fixable number from the same box navigates to the <strong>Issues</strong> tab, filtered to those fixable, yet ignored, issues only.<br></p><p><strong>Note:</strong> After you ignore an issue, it may take up to one hour before synchronizing with the data on the Summary tab of the Reports.</p> |

## **Filtering results**

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:

<figure><img src="https://2533899886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdwVZ6HOZriajCf5nXH%2Fuploads%2Fgit-blob-ea6a9cdb9310733b4671cb18ad335ec9835733a9%2Fimage%20(71).png?alt=media&#x26;token=463a990b-7c4f-4944-9f83-f53a2ff445d4" alt="Filter results"><figcaption><p>Filter results</p></figcaption></figure>

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.