Install the Snyk CLI
How to install the Snyk CLI across major operating systems
The Snyk CLI can be installed across all major operating systems using several different methods, depending on your existing toolset:
Package managers: Use tools like npm, Homebrew, or Scoop for a quick installation.
Docker: Run Snyk in a container for a consistent scanning environment.
GitHub Actions and CI/CD: Use pre-built integrations to automate scanning within your deployment pipelines.
Direct binary download: Download a standalone executable for Windows, MacOS, or Linux.
After you install the CLI, authenticate your Snyk account to start scanning your Snyk Projects. For more information, visit Authenticate to use the CLI.
The Snyk CLI does not natively support Windows Subsystem for Linux (WSL). You can install and use the CLI in a WSL environment, but Snyk does not guarantee compatability. Consequently, Snyk integrations that rely on the CLI, such as IDE extensions and CI/CD plugins, do not natively support WSL.
Common installation steps
Regardless of your choice of tool, there are common steps to ensuring your installation of the Snyk CLI is a success:
Install the Snyk CLI using your preferred method.
Verify the installed Snyk CLI version using
snyk --version.Authenticate the Snyk CLI to your account.
To learn how to upgrade the Snyk CLI for your chosen tool, visit Upgrade the Snyk CLI.
Installation methods
Package managers
Docker
Snyk provides a universal image and specialized images for specific package managers:
Universal:
snyk/snykLanguage specific:
snyk/snyk:node,snyk/snyk:maven,snyk/snyk:python, and so on.
Download the pre-packaged tools using the following command, specifying the universal or language specific image of your choosing:
Authenticate the connection. For more details, visit Authentication in Docker.
GitHub actions and CI/CD
Direct binary download
When using standalone executables, you must keep the Snyk CLI up to date manually.
Snyk provides standalone executables on the Snyk Content Delivery Network (CDN). For the latest download links, visit the latest release.json file.
For instructions on how to verify the shasum of downloaded binaries and their GPG signatures, visit Verifying CLI standalone binaries.
Last updated
Was this helpful?

