To have better control over your tests, you can pass the severity-threshold flag to the snyk test command with one of the supported options (low|medium|high). With this flag, only vulnerabilities of provided level or higher will be reported.
$ snyk test --severity-threshold=medium
Note: low option currently has the same effect as running without specifying the threshold, i.e. all vulnerabilities will be reported.
Since snyk test looks at the locally installed modules, it needs to be run after npm install or yarn install, and will seamlessly work with shrinkwrap, npm enterprise or any other custom installation logic you have.
Since snyk test looks at the locally installed modules, it needs to run after mvn install.
In order to use the CLI to test against your build.sbt manifest file, you’ll need to first install the sbt-dependency-graph plugin.
Running snyk test on your Scala projects without this plugin will throw the following error:
Error: Missing plugin sbt-dependency-graph (https://github.com/jrudolph/sbt-dependency-graph).
Please install it globally or on the current project and try again.
Since snyk test inspects the locally installed modules, it needs to run after the vendor/ folder has been populated via dep ensure or govendor sync. In addition, the GOPATH environment variable must be set correctly.
Since snyk test inspects the locally installed modules, it needs to run after the packages/(.NET) or obj/(.NET Core) folder has been populated via Visual Studio or dotnet restore.
The CLI does not currently auto-detect .sln files, so for .NET and .NET Core projects you can specify in the --file parameter the location of the solution file and the CLI will run on all the projects it finds inside.
$ snyk test--file=myApp.sln
Since snyk test inspects the locally installed modules, it needs to run after the composer.lock file has been created by composer install.