View analysis results from Visual Studio extension
Last updated
Was this helpful?
Last updated
Was this helpful?
You can filter vulnerabilities by name or by severity.
Filter by name by typing the name of the vulnerability in the search bar.
Filter by severity by selecting one or more of the severities when you open the search bar filter.
Users can configure the Snyk extension using the Project settings.
Note that the Scan all projects option is enabled by default. It adds the --all-projects
option for Snyk CLI to scan all Projects by default.
For Projects using Git repositories or when you specify a reference folder, Snyk can filter the displayed issues to show only issues introduced in the working branch.
This functionality reduces noise and allows you to focus only on current changes. This helps prevent issues early, thus unblocking your CI/CD pipeline and speeding up your deliveries.
The logic uses your local Git repository or any folder to compare the current findings with those in a base branch or reference folder. Net new issues scanning (delta scanning) shows you the difference between the two branches or folders, highlighting only the new issues.
In version 2.1.0 and later, you can choose any folder as your base for scanning.
To apply the filter and only see the new issues, use the total/new toggle in the summary panel.
The net new issues feature can also be enabled in the scan settings for the Visual Studio extension.
For newly created feature branches, there will be no reported issues. That is an intended state, that developers would aim for, as shown in the screen image that follows:
The base branch is usually automatically determined for each Git repository.
You may change the base branch or base folder by following these steps, as illustrated in the screen imaget that follows:
Toggle the total/new filter in the summary panel
Click on the top-level node in the Issues tree to change the branch or directory.
Use the dropdown selection to choose any branch or reference folder.