Skip to content

Commit 69a8327

Browse files
JackuBJackuB
committedNov 17, 2020
feat: new —help documentation
·
v1.1296.0v1.428.0
1 parent d08bc49 commit 69a8327

21 files changed

+578
-0
lines changed
 

‎help/commands-docs/_ENVIRONMENT.md

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
## ENVIRONMENT
2+
3+
You can set these environment variables to change CLI run settings. These keys will override settings in your `snyk config`:
4+
5+
- `SNYK_TOKEN`:
6+
Snyk authorization token. Setting this envvar will override the token that may be available in your `snyk config` settings.
7+
8+
[How to get your account token](https://snyk.co/ucT6J)<br />
9+
[How to use Service Accounts](https://snyk.co/ucT6L)<br />
10+
11+
- `SNYK_API`:
12+
Sets API host to use for Snyk requests. Useful for on-premise instances and configuring proxies.
13+
14+
- `SNYK_CFG_`<KEY>:
15+
Allows you to override any key that's also available as `snyk config` option.

‎help/commands-docs/_EXAMPLES.md

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
## EXAMPLES
2+
3+
- `Authenticate in your CI without user interaction`:
4+
\$ snyk auth MY_API_TOKEN
5+
- `Test a project in current folder for known vulnerabilities`:
6+
\$ snyk test
7+
- `Test a specific dependency for vulnerabilities`:
8+
\$ snyk test ionic@1.6.5
9+
10+
More examples:
11+
12+
$ snyk test --show-vulnerable-paths=false
13+
$ snyk monitor --org=my-team
14+
$ snyk monitor --project-name=my-project
15+
16+
### Container scanning
17+
18+
See `snyk container --help` for more details and examples:
19+
20+
$ snyk container test ubuntu:18.04 --org=my-team
21+
$ snyk container test app:latest --file=Dockerfile --policy-path=path/to/.snyk
22+
$ snyk test --yarn-workspaces --detection-depth=4 --strict-out-of-sync=false
23+
24+
### Infrastructure as Code (IAC) scanning
25+
26+
See `snyk iac --help` for more details and examples:
27+
28+
$ snyk iac test /path/to/Kubernetes.yaml
29+
$ snyk iac test /path/to/terraform_file.tf

‎help/commands-docs/_EXIT_CODES.md

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
## EXIT CODES
2+
3+
Possible exit codes and their meaning:
4+
5+
**0**: success, no vulns found<br />
6+
**1**: action_needed, vulns found<br />
7+
**2**: failure, try to re-run command<br />
8+
**3**: failure, no supported projects detected<br />

‎help/commands-docs/_NOTICES.md

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
## NOTICES
2+
3+
### Snyk API usage policy
4+
5+
The use of Snyk's API, whether through the use of the 'snyk' npm package or otherwise, is subject to the [terms & conditions](https://snyk.co/ucT6N)

‎help/commands-docs/_SNYK_COMMAND_HEADER.md

+51
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
# snyk(1) -- CLI and build-time tool to find & fix known vulnerabilities in open-source dependencies
2+
3+
## SYNOPSIS
4+
5+
`snyk` \[<COMMAND>] \[<SUBCOMMAND>] \[<OPTIONS>] \[<PACKAGE>] \[-- <COMPILER_OPTIONS>]
6+
7+
## DESCRIPTION
8+
9+
Snyk helps you find, fix and monitor known vulnerabilities in open-source dependencies.<br />
10+
For more information see https://snyk.io
11+
12+
### Not sure where to start?
13+
14+
1. authenticate with `$ snyk auth`
15+
2. test your local project with `$ snyk test`
16+
3. get alerted for new vulnerabilities with `$ snyk monitor`
17+
18+
## COMMANDS
19+
20+
To see command-specific flags and usage, see `help` command, e.g. `snyk container --help`.
21+
Available top-level CLI commands:
22+
23+
- `auth` \[<API_TOKEN>\]:
24+
Authenticate Snyk CLI with a Snyk account
25+
26+
- `test`:
27+
Test local project for vulnerabilities
28+
29+
- `monitor`:
30+
Snapshot and continuously monitor your project
31+
32+
- `container`:
33+
Test container images for vulnerabilities. See `snyk container --help` for full instructions.
34+
35+
- `iac`:
36+
Find security issues in your Infrastructure as Code files. See `snyk iac --help` for full instructions.
37+
38+
- `config`:
39+
Manage Snyk CLI configuration
40+
41+
- `protect`:
42+
Applies the patches specified in your .snyk file to the local file system
43+
44+
- `policy`:
45+
Display the .snyk policy for a package.
46+
47+
- `ignore`:
48+
Modifies the .snyk policy to ignore stated issues
49+
50+
- `wizard`:
51+
Configure your policy file to update, auto patch and ignore vulnerabilities. Snyk wizard updates your .snyk file.

‎help/commands-docs/_SNYK_COMMAND_OPTIONS.md

+176
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,176 @@
1+
## OPTIONS
2+
3+
To see command-specific flags and usage, see `help` command, e.g. `snyk container --help`.
4+
For advanced usage, we offer language and context specific flags, listed further down this document.
5+
6+
- `--all-projects`:
7+
(only in `test` and `monitor` commands)
8+
Auto-detect all projects in working directory
9+
10+
- `--detection-depth`=<DEPTH>:
11+
(only in `test` and `monitor` commands)
12+
Use with --all-projects or --yarn-workspaces to indicate how many sub-directories to search. `DEPTH` must be a number.
13+
14+
Default: 4 (the current working directory and 3 sub-directories)
15+
16+
- `--exclude`=<DIRECTORY>[,<DIRECTORY>]...>:
17+
(only in `test` and `monitor` commands)
18+
Can be used with --all-projects and --yarn-workspaces to indicate sub-directories to exclude. Directories must be comma separated.
19+
20+
If using with `--detection-depth` exclude ignores directories at any level deep.
21+
22+
- `--prune-repeated-subdependencies`, `-p`:
23+
(only in `test` and `monitor` commands)
24+
Prune dependency trees, removing duplicate sub-dependencies.
25+
Will still find all vulnerabilities, but potentially not all of the vulnerable paths.
26+
27+
- `--print-deps`:
28+
(only in `test` and `monitor` commands)
29+
Print the dependency tree before sending it for analysis.
30+
31+
- `--remote-repo-url`=<URL>:
32+
Set or override the remote URL for the repository that you would like to monitor.
33+
34+
- `--dev`:
35+
Include devDependencies.
36+
37+
Default: scan only production dependencies
38+
39+
- `--org`=<ORG_NAME>:
40+
Specify the <ORG_NAME> to run Snyk commands tied to a specific organization. This will influence where will new projects be created after running `monitor` command, some features availability and private tests limits.
41+
If you have multiple organizations, you can set a default from the CLI using:
42+
43+
`$ snyk config set org`=<ORG_NAME>
44+
45+
Setting a default will ensure all newly monitored projects will be created
46+
under your default organization. If you need to override the default, you can use the `--org`=<ORG_NAME> argument.
47+
48+
Default: uses <ORG_NAME> that sets as default in your [Account settings](https://app.snyk.io/account)
49+
50+
- `--file`=<FILE>:
51+
Sets a package file.
52+
53+
When testing locally or monitoring a project, you can specify the file that Snyk should inspect for package information. When ommitted Snyk will try to detect the appropriate file for your project.
54+
55+
- `--ignore-policy`:
56+
Ignores all set policies. The current policy in `.snyk` file, Org level ignores and the project policy on snyk.io.
57+
58+
- `--trust-policies`:
59+
Applies and uses ignore rules from your dependencies' Snyk policies, otherwise ignore policies are only shown as a suggestion.
60+
61+
- `--show-vulnerable-paths`=none|some|all:
62+
Display the dependency paths from the top level dependencies, down to the vulnerable packages. Doesn't affect output when using JSON `--json` output.
63+
64+
Default: <some> (a few example paths shown)
65+
<false> is an alias for <none>.
66+
67+
- `--project-name`=<PROJECT_NAME>:
68+
Specify a custom Snyk project name.
69+
70+
- `--policy-path`=<PATH_TO_POLICY_FILE>`:
71+
Manually pass a path to a snyk policy file.
72+
73+
- `--json`:
74+
Prints results in JSON format.
75+
76+
- `--json-file-output`=<OUTPUT_FILE_PATH>:
77+
(only in `test` command)
78+
Save test output in JSON format directly to the specified file, regardless of whether or not you use the `--json` option.
79+
This is especially useful if you want to display the human-readable test output via stdout and at the same time save the JSON format output to a file.
80+
81+
- `--severity-threshold`=low|medium|high:
82+
Only report vulnerabilities of provided level or higher.
83+
84+
- `--fail-on`=all|upgradable|patchable:
85+
Only fail when there are vulnerabilities that can be fixed.
86+
87+
<all> fails when there is at least one vulnerability that can be either upgraded or patched.
88+
<upgradable> fails when there is at least one vulnerability that can be upgraded.
89+
<patchable> fails when there is at least one vulnerability that can be patched.
90+
91+
If vulnerabilities do not have a fix and this option is being used, tests will pass.
92+
93+
- `--dry-run`:
94+
(only in `protect` command)
95+
Don't apply updates or patches during `protect` command run.
96+
97+
- `--` \[<COMPILER_OPTIONS>\]:
98+
Pass extra arguments directly to Gradle or Maven.
99+
E.g. `snyk test -- --build-cache`
100+
101+
Below are flags that are influencing CLI behavior for specific projects, languages and contexts:
102+
103+
### Maven options
104+
105+
- `--scan-all-unmanaged`:
106+
Auto detects maven jars and wars in given directory. Individual testing can be done with `--file`=<JAR_FILE_NAME>
107+
108+
- `--reachable`:
109+
(only in `test` and `monitor` commands)
110+
Analyze your source code to find which vulnerable
111+
functions and packages are called.
112+
113+
- `--reachable-timeout`=<TIMEOUT>:
114+
The amount of time (in seconds) to wait for Snyk to gather reachability data. If it takes longer than <TIMEOUT>, Reachable Vulnerabilities are not reported. This does not affect regular test or monitor output.
115+
116+
Default: 300 (5 minutes).
117+
118+
### Gradle options
119+
120+
[More information about Gradle CLI options](https://snyk.co/ucT6P)
121+
122+
- `--sub-project`=<NAME>, `--gradle-sub-project`=<NAME>:
123+
For Gradle "multi project" configurations, test a specific sub-project.
124+
125+
- `--all-sub-projects`:
126+
For "multi project" configurations, test all sub-projects.
127+
128+
- `--configuration-matching`=<CONFIGURATION_REGEX>:
129+
Resolve dependencies using only configuration(s) that match the provided Java regular expression, e.g. `^releaseRuntimeClasspath$`.
130+
131+
- `--configuration-attributes`=<ATTRIBUTE>[,<ATTRIBUTE>]...:
132+
Select certain values of configuration attributes to resolve the dependencies. E.g. `buildtype:release,usage:java-runtime`
133+
134+
### .Net & NuGet options
135+
136+
- `--assets-project-name`:
137+
When monitoring a .NET project using NuGet `PackageReference` use the project name in project.assets.json, if found.
138+
139+
- `--packages-folder`:
140+
Custom path to packages folder
141+
142+
### npm options
143+
144+
- `--strict-out-of-sync`=true|false:
145+
Control testing out of sync lockfiles.
146+
147+
Default: true
148+
149+
### Yarn options
150+
151+
- `--strict-out-of-sync`=true|false:
152+
Control testing out of sync lockfiles.
153+
154+
Default: true
155+
156+
- `--yarn-workspaces`:
157+
(only in `test` and `monitor` commands)
158+
Detect and scan yarn workspaces. You can specify how many sub-directories to search using `--detection-depth` and exclude directories using `--exclude`.
159+
160+
### CocoaPods options
161+
162+
- `--strict-out-of-sync`=true|false:
163+
Control testing out of sync lockfiles.
164+
165+
Default: false
166+
167+
### Python options
168+
169+
- `--command`=<COMMAND>:
170+
Indicate which specific Python commands to use based on Python version. The default is `python` which executes your systems default python version. Run 'python -V' to find out what version is it. If you are using multiple Python versions, use this parameter to specify the correct Python command for execution.
171+
172+
Default: `python`
173+
Example: `--command=python3`
174+
175+
- `--skip-unresolved`=true|false:
176+
Allow skipping packages that are not found in the environment.

‎help/commands-docs/_SNYK_GLOBAL_OPTIONS.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
### Flags available accross all commands
2+
3+
- `--insecure`:
4+
Ignore unknown certificate authorities.
5+
6+
- `-d`:
7+
Output debug logs.
8+
9+
- `--quiet`, `-q`:
10+
Silence all output.
11+
12+
- `--version`, `-v`:
13+
Prints versions.
14+
15+
- \[<COMMAND>\] `--help`, `--help` \[<COMMAND>\], `-h`:
16+
Prints a help text. You may specify a <COMMAND> to get more details.

‎help/commands-docs/auth.md

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# snyk-auth(1) -- Authenticate Snyk CLI with a Snyk account
2+
3+
## SYNOPSIS
4+
5+
`snyk` `auth` \[<API_TOKEN>\] \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Authenticate Snyk CLI with a Snyk account. Running `$ snyk auth` without an <API_TOKEN> will open a browser window and asks you to login with Snyk account and authorize. When inputting an <API_TOKEN>, it will be validated with Snyk API.
10+
11+
When running in a CI environment <API_TOKEN> is required.
12+
13+
## OPTIONS
14+
15+
- \[<API_TOKEN>\]:
16+
Your Snyk token. May be an user token or a service account.<br />
17+
[How to get your account token](https://snyk.co/ucT6J)<br />
18+
[How to use Service Accounts](https://snyk.co/ucT6L)<br />

‎help/commands-docs/config.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# snyk-config(1) -- Manage Snyk CLI configuration
2+
3+
## SYNOPSIS
4+
5+
`snyk` `config` `get|set|clear` \[<KEY>\[=<VALUE>\]\] \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Manage your local Snyk CLI config file.
10+
11+
This command does not manage the `.snyk` file that's part of your project. See `snyk policy`, `snyk ignore` or `snyk wizard`.
12+
13+
## COMMANDS
14+
15+
- `get` <KEY>:
16+
Print a config value.
17+
18+
- `set` <KEY>=<VALUE>:
19+
Create a new config value.
20+
21+
- `unset` <KEY>:
22+
Remove a config value.
23+
24+
- `clear`:
25+
Remove all config values.
26+
27+
## OPTIONS
28+
29+
### Supported <KEY> values
30+
31+
- `api`:
32+
API token to use when calling Snyk API.
33+
34+
- `endpoint`:
35+
Defines the API endpoint to use.
36+
37+
- `disable-analytics`:
38+
Turns off analytics reporting.

‎help/commands-docs/container.md

+57
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
# snyk-container(1) -- Test container images for vulnerabilities
2+
3+
## SYNOPSIS
4+
5+
`snyk` `container` \[<COMMAND>\] \[<OPTIONS>\] \[<IMAGE>\]
6+
7+
## DESCRIPTION
8+
9+
Find vulnerabilities in your container images.
10+
11+
## COMMANDS
12+
13+
- `test`:
14+
Test for any known vulnerabilities.
15+
16+
- `monitor`:
17+
Record the state of dependencies and any vulnerabilities on snyk.io.
18+
19+
## OPTIONS
20+
21+
- `--exclude-base-image-vulns`:
22+
Exclude from display base image vulnerabilities.
23+
24+
- `--file`=<FILE_PATH>:
25+
Include the path to the image's Dockerfile for more detailed advice.
26+
27+
- `--platform`=<PLATFORM>:
28+
For multi-architecture images, specify the platform to test.
29+
[linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7 orlinux/arm/v6]
30+
31+
- `--json`:
32+
Prints results in JSON format.
33+
34+
- `--json-file-output`=<OUTPUT_FILE_PATH>:
35+
(only in `test` command)
36+
Save test output in JSON format directly to the specified file, regardless of whether or not you use the `--json` option.
37+
This is especially useful if you want to display the human-readable test output via stdout and at the same time save the JSON format output to a file.
38+
39+
- `--sarif`:
40+
Return results in SARIF format.
41+
42+
- `--sarif-file-output`=<OUTPUT_FILE_PATH>:
43+
(only in `test` command)
44+
Save test output in SARIF format directly to the <OUTPUT_FILE_PATH> file, regardless of whether or not you use the `--sarif` option.
45+
This is especially useful if you want to display the human-readable test output via stdout and at the same time save the SARIF format output to a file.
46+
47+
- `--print-deps`:
48+
Print the dependency tree before sending it for analysis.
49+
50+
- `--project-name`=<PROJECT_NAME>:
51+
Specify a custom Snyk project name.
52+
53+
- `--policy-path`=<PATH_TO_POLICY_FILE>`:
54+
Manually pass a path to a snyk policy file.
55+
56+
- `--severity-threshold`=low|medium|high:
57+
Only report vulnerabilities of provided level or higher.

‎help/commands-docs/help.md

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# snyk-help(1) -- Prints help topics
2+
3+
## SYNOPSIS
4+
5+
`snyk` `help` \[<TOPIC>\] \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Prints help information. Pass in name of a command as <TOPIC>.
10+
11+
## OPTIONS

‎help/commands-docs/iac-examples.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
## EXAMPLES
2+
3+
[For more information see IaC help page](https://snyk.co/ucT6Q)
4+
5+
- `Test kubernetes file`:
6+
\$ snyk iac test /path/to/Kubernetes.yaml
7+
8+
- `Test terraform file`:
9+
\$ snyk iac test /path/to/terraform_file.tf

‎help/commands-docs/iac.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# snyk-iac(1) -- Find security issues in your Infrastructure as Code files
2+
3+
## SYNOPSIS
4+
5+
`snyk` `iac` \[<COMMAND>\] \[<OPTIONS>\] <PATH>
6+
7+
## DESCRIPTION
8+
9+
Find security issues in your Infrastructure as Code files.
10+
11+
[For more information see IaC help page](https://snyk.co/ucT6Q)
12+
13+
## COMMANDS
14+
15+
- `test`:
16+
Test for any known issue.
17+
18+
## OPTIONS
19+
20+
- `--severity-threshold`=low|medium|high:
21+
Only report vulnerabilities of provided level or higher.
22+
23+
- `--json`:
24+
Prints results in JSON format.
25+
26+
- `--json-file-output`=<OUTPUT_FILE_PATH>:
27+
(only in `test` command)
28+
Save test output in JSON format directly to the specified file, regardless of whether or not you use the `--json` option.
29+
This is especially useful if you want to display the human-readable test output via stdout and at the same time save the JSON format output to a file.
30+
31+
- `--sarif`:
32+
Return results in SARIF format.
33+
34+
- `--sarif-file-output`=<OUTPUT_FILE_PATH>:
35+
(only in `test` command)
36+
Save test output in SARIF format directly to the <OUTPUT_FILE_PATH> file, regardless of whether or not you use the `--sarif` option.
37+
This is especially useful if you want to display the human-readable test output via stdout and at the same time save the SARIF format output to a file.

‎help/commands-docs/ignore-examples.md

+4
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
## EXAMPLES
2+
3+
- `Ignore a specific vulnerability`:
4+
\$ snyk ignore --id='npm:qs:20170213' --expiry='2021-01-10' --reason='Module not affected by this vuln'

‎help/commands-docs/ignore.md

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# snyk-ignore(1) -- Modifies the .snyk policy to ignore stated issues
2+
3+
## SYNOPSIS
4+
5+
`snyk` `ignore` `--id`=<ISSUE_ID> \[`--expiry`=<EXPIRY>\] \[`--reason`=<REASON>\] \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Ignore a certain issue, according to its snyk ID for all occurrences. This will update your local `.snyk` to contain a similar block:
10+
11+
```yaml
12+
ignore:
13+
'<ISSUE_ID>':
14+
- '*':
15+
reason: <REASON>
16+
expires: <EXPIRY>
17+
```
18+
19+
## OPTIONS
20+
21+
- `--id`=<ISSUE_ID>:
22+
Snyk ID for the issue to ignore. Required.
23+
24+
- `--expiry`=<EXPIRY>:
25+
Expiry date, according to [RFC2822](https://tools.ietf.org/html/rfc2822)
26+
27+
- `--reason`=<REASON>:
28+
Human-readable <REASON> to ignore this issue.

‎help/commands-docs/monitor.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# snyk-monitor(1) -- Snapshot and continuously monitor your project
2+
3+
## SYNOPSIS
4+
5+
`snyk` `monitor` \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Create a project on the Snyk website that will be continuously monitored for new vulnerabilities. After running this command you will see it by logging in to the website and viewing Your projects.

‎help/commands-docs/policy.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# snyk-policy(1) -- Display the .snyk policy for a package
2+
3+
## SYNOPSIS
4+
5+
`snyk` `policy` \[<PATH_TO_POLICY_FILE>\] \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Displays a `.snyk` policy file.
10+
11+
## OPTIONS
12+
13+
- <PATH_TO_POLICY_FILE>:
14+
Manually pass a path to a snyk policy file.

‎help/commands-docs/protect.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# snyk-protect(1) -- Applies the patches specified in your .snyk file to the local file system
2+
3+
## SYNOPSIS
4+
5+
`snyk` `protect` \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
`$ snyk protect` is used to apply patches to your vulnerable dependencies. It's useful after opening a fix pull request from our website (GitHub only) or after running snyk wizard on the CLI. snyk protect reads a .snyk policy file to determine what patches to apply.
10+
11+
## OPTIONS
12+
13+
- `--dry-run`:
14+
Don't apply updates or patches when running.

‎help/commands-docs/test.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# snyk-test(1) -- test local project for vulnerabilities
2+
3+
## SYNOPSIS
4+
5+
`snyk` `test` \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Test command checks locally installed projects for vulnerabilities. It tries to autodetect supported manifest files with dependencies and test those.

‎help/commands-docs/wizard.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# snyk-wizard(1) -- Configure your policy file to update, auto patch and ignore vulnerabilities
2+
3+
## SYNOPSIS
4+
5+
`snyk` `wizard` \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Snyk's wizard will:
10+
11+
- Enumerate your local dependencies and query Snyk's servers for vulnerabilities
12+
- Guide you through fixing found vulnerabilities
13+
- Create a .snyk policy file to guide snyk commands such as `test` and `protect`
14+
- Remember your dependencies to alert you when new vulnerabilities are disclosed
15+
16+
## OPTIONS

‎help/commands-docs/woof.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# snyk-woof(1) -- W00f
2+
3+
## SYNOPSIS
4+
5+
`snyk` `woof` \[<OPTIONS>\]
6+
7+
## DESCRIPTION
8+
9+
Easter egg that prints a Patch ascii art.
10+
11+
## OPTIONS
12+
13+
- `--language`=<LANGUAGE>:
14+
Woof in a specific language. <LANGUAGE> should be a ISO 639-1 code.

0 commit comments

Comments
 (0)
Please sign in to comment.