Scan and maintain Projects using the CLI (examples)

How to scan and maintain Projects with the Snyk CLI

This group of pages provides detailed "how-to" information for the Snyk CLI.

• The CLI tools provide ways to perform tasks that cannot be done using CLI commands and options.

• Use Snyk Open Source from the CLI, Analyze code with the Snyk Code CLI, and Use Snyk Container from the CLI explain how to perform basic operations with Snyk Open Source, Snyk Code, and Snyk Container using the CLI.

The remaining pages address Scanning Projects, Monitoring Projects, and Maintaining Projects. The pages are arranged in alphabetical order by keyword.

Scanning Projects

• The .snyk file

• A .snyk policy file in a different directory from the manifest file

• Failing builds in Snyk CLI

• Ignore vulnerabilties using Snyk CLI

• Invalid string length error when scanning projects

• Scan all unmanaged JAR files

• How to select the organization to use in the CLI

• Setup.py file failing to scan or finding zero dependencies

• Severity thresholds for CLI tests

• Test public npm packages before use

• CLI test results

• Differences in vulnerability counts across environments

Monitoring Projects

• Monitor your projects at regular intervals

• Group projects for monitoring

Maintaining Projects

• Log4shell command use

• @snyk/protect package

• Fix vulnerabilities using the Snyk CLI