Ignore issues

You can set ignores individually or as actions - see Setting ignores for details.
If you do not want to fix a vulnerability or license issue, and you do not want to see that issue in scan results, Snyk allows you to ignore the issue, either temporarily or permanently.

Deciding to ignore issues

The best practice is to fix or patch vulnerabilities or to remove the vulnerable dependency.
However, you may want to suppress an issue for any of the following reasons:
  • There is no fix.
  • The issue is not relevant to the Project. for example, a distributed denial-of-service (DDoS) attack for an internal service.
If an issue has a path that makes it non-exploitable, it is still best to fix the issue. A vulnerability that is not exploitable today may become exploitable in future.

Setting ignores

Issues can be ignored and viewed through the following means:

Ignoring issues in the Web UI

Each issue card has an Ignore button that opens a dialog where you can select how or why you want to ignore the issue and how long to ignore it.
Ignore dialog from issue card
Ignore dialog from issue card
You can select Not vulnerable for any issue that is not exploitable at the time you create the ignore.
If you select Ignore temporarily, then you can check the Until fix is available checkbox:
Ignore temporarily
Ignore temporarily
This is checked by default if there is currently no fix available for this issue. The vulnerability resurfaces as soon as Snyk has a fix for it, and optionally you can give additional details on why you are ignoring the issue.
An issue is ignored until either of the conditions occurs: the ignore period expires, or the vulnerability becomes fixable.
An issue ignored within an Open Source or Code Project in the Snyk web UI will be reflected and not flagged in any consecutive PR check across all branches of that Project.
When you ignore an issue in the Snyk Web UI, the issue shows who ignored it and allow you to edit or unignore it.
Ignore set in the Snyk Web UI
Ignore set in the Snyk Web UI
For more information, see the training: Ignoring issues.

Ignoring issues in the CLI

You can suppress issues through the CLI by using the snyk ignore command, for example:
snyk ignore --id='npm:braces:20180219' --expiry='2018-04-01' --reason='testing'
For more information, see the ignore command help and Ignore vulnerabilities using Snyk CLI.
When you use snyk ignore, the .snyk policy file is updated with the path and reason given if one was provided. For example:
- moment:
reason: The reason given
expires: '2017-12-29T16:10:16.946Z'

Scanning from the CLI or CI/CD, ignoring in the Web UI

Ignores between a CLI or CI/CD run and the Snyk UI are synchronized as follows:
  1. 1.
    A Project is scanned and pushed to the UI using snyk monitor.
  2. 2.
    You see the results of the scan and choose to ignore an issue.
  3. 3.
    The issue is ignored when running snyk test or snyk monitor in the CI/CD or CLI.
Refer to the following example. Issues are identified as CI/CLI, meaning the Project was imported from snyk monitor. The issue is npmconf. It is Not vulnerable, and the user can select Ignore.
Project imported from snyk monitor, ignore set in the Web UI
Project imported from snyk monitor, ignore set in the Web UI
The following shows snyk test results before ignoring in the Web UI:
Snyk test results before ignoring in the Web UI
Snyk test results before ignoring in the Web UI
The following shows snyk test results after ignoring in the Web UI:
Snyk test results after ignoring in the Web UI
Snyk test results after ignoring in the Web UI
This example shows what happens if you ignore the Project imported by snyk monitor from the CLI or CI/CD.
The same repository imported from the SCM is considered to be a different Project, and any ignore on an SCM Project does not impact the results of snyk test from the CLI or a CI/CD. SCM and CI Projects behave as two standalone Projects.

Ignoring issues with the .snyk file

For all Projects, you can ignore the vulnerability by creating a .snyk YAML file.
A .snyk file
For example, if you want to ignore the vulnerability with SNYK ID SNYK-RUBY-FASTREADER-20085 in fastreader, with the reason “No fix available” until 01 Jan 2024, you would write the following:
version: v1.5.0
- '* > fastreader':
reason: 'No fix available'
expires: '2024-01-01T00:00:00.000Z'
For more information, see The .snyk file including the section about .snyk files in monorepos and .snyk files in different directories from manifest files.

Ignoring issues with policy actions

You can set Security policies actions to ignore all vulnerabilities that match the conditions specified in a policy rule.
For more information, see Security policies: Actions.

Snyk Code: ignoring issues

For Snyk Code, the ignore functionality may capture a wider range of issues than other products.
Snyk Code's static code analysis transforms the input code into an intermediate representation, which captures the flow of code but abstracts away some details. Snyk Code uses this representation to recognize the same issue even when you refactor your code or rename a variable.
Thus when you ignore an issue, Snyk Code can also ignore that issue if it occurs in multiple places in your code, even with minor code changes. This avoids generating multiple duplicate reports for pieces of code with the same ignored issue.
As an example, the following two code snippets (despite textual differences) denounce the same issue, as the developer only renamed the variables:
var fs = require('fs');
var logFileName = req.query.file || 'standard_log.log';
var logfile = fs.readFile(logFileName, "utf8", function(err, data) {...
var filesystem = require('fs');
var generalLogFileName = req.query.file || 'standard_log.log';
var handleLogFile = filesystem.readFile(generalLogFileName, "utf8", function(err, data) {...

Snyk IaC: ignoring issues

When scanning your IaC configuration files using snyk iac test you can ignore issues that are not relevant to you by using The .snyk file.
Snyk recommends storing and versioning the .snyk file in the root of your working directory, where you store your IaC configuration files.
For more information, see IaC ignores using the .snyk policy file.

Configure ignore settings

Suppressing vulnerabilities carries a level of risk, so you can make this function available to admins only as follows
  1. 1.
    Go to your Organization settings > General, then navigate in the Ignores section
  2. 2.
    Under Ability to ignore an issue or edit the ignore settings on an issue, select Admin users only. Note that this also disables ignores from being added via the CLI.
  3. 3.
    Under Require reason for each ignore, you can also choose to set the more details field to be a required field when an issue is being ignored, ensuring the user enters a reason for each ignore.
  4. 4.
    Select Update to make the changes.
Update ignore settings
Update ignore settings

Using ignores in reports

If you have access to the Snyk Reports feature, you can also see an overview of how many issues in your Organization’s Projects are ignored, along with an option to filter these so you can drill down into each one. If the issue was ignored in the Snyk Web UI, Snyk includes a credit so you can see who initiated it.
For more information, see Reports.