SupportAPI docsProduct updatesSign up for free
Search…
Snyk User Documentation
Introducing Snyk
Implementing Snyk in your teams
Getting started
Snyk Web UI
Snyk CLI
Getting started with the CLI
Scan and maintain projects using the CLI
The .snyk file
A .snyk policy file in a different directory from the manifest file
Failing of builds in Snyk CLI
Automatic fixing with snyk fix
Ignore vulnerabilities using Snyk CLI
Log4shell command use
Monitor your projects at regular intervals
Group projects for monitoring
@snyk/protect package
Scan all unmanaged JAR files
Setup.py file failing to scan or finding zero dependencies
Severity thresholds for CLI tests
Test public npm packages before use
Test public repositories before use
CLI test results
CLI commands and options summary
CLI help
Install or update the Snyk CLI
Authenticate the CLI with your account
Configure the Snyk CLI
Snyk API
Snyk for IDEs
Snyk Apps
Snyk Integrations
SNYK PRODUCTS
Snyk Open Source
Snyk Code
Snyk Container
Snyk Infrastructure as Code
USING SNYK
Snyk Broker
User and group management
Fixing and prioritizing issues
Reports
Snyk Tools
SNYK INFO
Disclosing vulnerabilities
How Snyk handles your data
Snyk Partner workshops
Powered By GitBook
Monitor your projects at regular intervals
By using the test command and the @snyk/protect package (replaced the snyk protect command), you are well set up to address known vulnerabilities. To address new vulnerabilities, which are constantly disclosed, use snyk monitor.
Just before you deploy, run snyk monitor in your project directory:
cd ~/projects/myproject/ snyk monitor
This sends a snapshot of your current dependencies to your Snyk dashboard, so Snyk can notify you about newly disclosed vulnerabilities in those dependencies, or when a previously unavailable patch or upgrade path is created. If you take multiple snapshots of the same project, Snyk alerts you only to new information about the latest snapshot.
Log in to the Snyk Web UI, and go to your organization's project page (https://app.snyk.io/monitor/) to see the latest snapshot and history of your project.
Previous
Log4shell command use
Next
Group projects for monitoring
Last modified 8d ago
Export as PDF
Copy link
Edit on GitHub