snyk monitor [<OPTIONS>]
snyk monitor
command creates a project in your Snyk account to be continuously monitored for open source vulnerabilities and license issues. After running this command, log in to the Snyk website and view your projects to see the monitor.-d
option to output the debug logs.[<CONTEXT-SPECIFIC OPTIONS>]
which you specify last.--all-projects
--detection-depth=<DEPTH>
--all-projects
or --yarn-workspaces
to indicate how many subdirectories to search. DEPTH
must be a number, 1
or greater; zero (0) is the current directory.--detection-depth=3
limits search to the specified directory (or the current directory if no <PATH>
is specified) plus three levels of subdirectories; zero (0) is the current directory.--exclude=<NAME>[,<NAME>]...>
--all-projects
and --yarn-workspaces
to indicate directory names and file names to exclude. Must be comma separated.$ snyk test --all-projects --exclude=dir1,file2
--prune-repeated-subdependencies
, -p
--print-deps
--remote-repo-url=<URL>
--dev
devDependencies
in npm or :development
dependencies in Gemfile.--org=<ORG_ID>
<ORG_ID>
to run Snyk commands tied to a specific organization. The <ORG_ID>
influences some features availability and private test limits.$ snyk config set org=<ORG_
ID>
--org=<ORG_ID>
option.--file=<FILE>
--package-manager=<PACKAGE_MANAGER_NAME>
--file=<FILE>
option is not standard. This allows Snyk to find the file.$ snyk monitor --file=req.txt --package-manager=pip
--unmanaged
--ignore-policy
.snyk
file, org level ignores, and the project policy on snyk.io.--trust-policies
--project-name=<PROJECT_NAME>
$ snyk monitor --project-name=my-project
--target-reference=<TARGET_REFERENCE>
--unmanaged
.--policy-path=<PATH_TO_POLICY_FILE>
.snyk
policy file.--json
--project-environment=<ENVIRONMENT>[,<ENVIRONMENT>]...>
--project-environment=
frontend, backend, internal, external, mobile, saas, onprem, hosted, distributed
--project-lifecycle=<LIFECYCLE>[,<LIFECYCLE>]...>
--project-lifecycle=
production, development, sandbox
--project-business-criticality=<BUSINESS_CRITICALITY>[,<BUSINESS_CRITICALITY>]...>
--project-business-criticality=
critical, high, medium, low
--project-tags=<TAG>[,<TAG>]...>
--project-tags=department=finance,team=alpha
To clear the project tags set --project-tags=
--tags=<TAG>[,<TAG>]...>
--project-tags
--scan-all-unmanaged
--file=<JAR_FILE_NAME>
--reachable
--all-projects
--reachable-timeout=<TIMEOUT>
<TIMEOUT>
, reachable vulnerabilities are not reported. This does not affect regular test or monitor output.--sub-project=<NAME>
, --gradle-sub-project=<NAME>
--all-sub-projects
--configuration-matching=<CONFIGURATION_REGEX>
^releaseRuntimeClasspath$
--configuration-attributes=<ATTRIBUTE>[,<ATTRIBUTE>]...
buildtype:release,usage:java-runtime
--reachable
--reachable-timeout=<TIMEOUT>
<TIMEOUT>
, reachable vulnerabilities are not reported. This does not affect regular test or monitor output.--init-script=<FILE
--assets-project-name
PackageReference
use the project name in project.assets.json
, if found.--packages-folder
--project-name-prefix=<PREFIX_STRING>
snyk monitor --file=my-project.sln --project-name-prefix=my-group/
.sln
files.--strict-out-of-sync=true|false
--strict-out-of-sync=true|false
--yarn-workspaces
--detection-depth
and exclude directories and files using --exclude
. Alternatively scan Yarn workspaces with other projects using --all-projects
--strict-out-of-sync=true|false
--command=<COMMAND>
python
which executes your default python version. Run 'python -V' to find out what version it is. If you are using multiple Python versions, use this parameter to specify the correct Python command for execution.python
Example: --command=python3
--skip-unresolved=true|false
--unmanaged
snyk monitor
options can be used with --unmanaged
.--org=<ORG_ID>
--json
--target-reference=<TARGET_REFERENCE>
--target-dir
snyk test --unmanaged
--max-depth
Usage: --max-depth=1
Specify the maximum level of archive extraction.--project-name=c-project
snyk monitor --unmanaged
command to override the default name Snyk gives your snapshots by entering the desired name.-- [<CONTEXT-SPECIFIC_OPTIONS>]
--
) after the complete Snyk command to pass options (arguments, flags) that follow directly to the build tool, for example Gradle or Maven.snyk <command> -- [<context-specific_options>]
snyk monitor -- --build-cache