snyk 1.695.0 → 1.696.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,289 +2,275 @@
2
2
  <img src="https://snyk.io/style/asset/logo/snyk-print.svg" />
3
3
  </p>
4
4
 
5
- <p align="center">
6
- <a href="https://snyk.io/docs/?utm_campaign=docs&utm_medium=github&utm_source=full_docs">Documentation</a> |
7
- <a href="https://snyk.io/test/">Test your project</a>
8
- </p>
5
+ # Snyk CLI
9
6
 
10
- <p align="center">
11
- Snyk helps you find, fix and monitor known vulnerabilities in open source
12
- </p>
7
+ [Snyk](https://snyk.io) scans and monitors your projects for security vulnerabilities.
13
8
 
14
- <p align="center">
15
- <a href="https://snyk.io/test/github/snyk/snyk"><img src="https://snyk.io/test/github/snyk/snyk/badge.svg" alt="Known Vulnerabilities"/></a>
16
- <a href="https://snyk.io/features/"><img src="https://badgen.net/npm/dm/snyk" alt="Monthly Downloads"/></a>
17
- <a href="https://snyk.io/advisor/npm-package/snyk"><img src="https://snyk.io/advisor/npm-package/snyk/badge.svg" alt="Snyk CLI on the Snyk Advisor></a>
18
- </p>
9
+ ![Snyk CLI screenshot](help/snyk-cli-screenshot.png)
19
10
 
20
- ---
11
+ # What is [Snyk](https://snyk.io)?
21
12
 
22
- ## What is Snyk?
13
+ [Snyk](https://snyk.io) is a developer-first cloud-native security tool.
14
+ It covers multiple areas of application security:
23
15
 
24
- <p align="center">
25
- <a href="https://youtu.be/4ng5usM6fd8">
26
- <img alt="What is Snyk?" src="https://i3.ytimg.com/vi/4ng5usM6fd8/maxresdefault.jpg" width="75%" height="75%" />
27
- </a>
28
- </p>
16
+ 1. [**Snyk Open Source**](https://snyk.io/product/open-source-security-management/): Find and automatically fix open source vulnerabilities
17
+ 2. [**Snyk Code**](https://snyk.io/product/snyk-code/): Find and fix vulnerabilities in your application code in real time
18
+ 3. [**Snyk Container**](https://snyk.io/product/container-vulnerability-management/): Find and fix vulnerabilities in container images and Kubernetes applications
19
+ 4. [**Snyk Infrastructure as Code**](https://snyk.io/product/infrastructure-as-code-security/): Find and fix insecure configurations in Terraform and Kubernetes code
20
+
21
+ [Learn more about what Snyk can do and sign up for a free account »](https://snyk.io)
22
+
23
+ # What is Snyk CLI?
24
+
25
+ Snyk CLI brings the functionality of [Snyk](https://snyk.io) into your development workflow. It can be run locally or in your CI/CD pipeline to scan your projects for security issues.
26
+
27
+ ## Supported languages and tools
29
28
 
30
- ## Table Of Contents:
29
+ Snyk supports many languages and tools, including Java, .NET, JavaScript, Python, Golang, PHP, C/C++, Ruby, Scala and more. See our [Language Support documentation](https://support.snyk.io/hc/en-us/articles/360020352437-Language-support-summary).
31
30
 
32
- - [Installation](#installation)
33
- - [CLI](#cli)
34
- - [Features](#features)
35
- - [Docker](#docker)
36
- - [Badge](#badge)
31
+ CLI also supports [Docker scanning](https://support.snyk.io/hc/en-us/articles/360003946897-Snyk-Container-security-overview) and [Terraform, k8s and other Infrastructure as Code files scanning](https://support.snyk.io/hc/en-us/categories/360001342678-Infrastructure-as-code).
37
32
 
38
- ## Installation
33
+ ---
34
+
35
+ # Install Snyk CLI
39
36
 
40
- 1. Install the Snyk utility using `npm install -g snyk`.
41
- 2. Once installed you will need to authenticate with your Snyk account: `snyk auth`
37
+ Snyk CLI can be installed through multiple channels.
42
38
 
43
- For more detail on how to authenticate take a look at the [CLI authentication](https://snyk.io/docs/using-snyk#authentication?utm_campaign=docs&utm_medium=github&utm_source=CLI_authentication) section of the Snyk documentation.
39
+ ## Install with npm or Yarn
44
40
 
45
- ## CLI
41
+ [Snyk CLI is available as an npm package](https://www.npmjs.com/package/snyk). If you have Node.js installed locally, you can install it by running:
46
42
 
47
- ```console
48
- snyk [options] [command] [package]
43
+ ```bash
44
+ npm install snyk@latest -g
49
45
  ```
50
46
 
51
- Run `snyk --help` to get a quick overview of all commands or for full details on the CLI read the snyk.io [CLI docs](https://snyk.io/docs/using-snyk?utm_campaign=docs&utm_medium=github&utm_source=cli).
47
+ or if you are using Yarn:
52
48
 
53
- The package argument is optional. If no package is given, Snyk will run the command against the current working directory allowing you to test your non-public applications.
49
+ ```bash
50
+ yarn global add snyk
51
+ ```
54
52
 
55
- ## Features
53
+ ## More installation methods
56
54
 
57
- - **Find** known vulnerabilities by running `snyk test` on a project either as a one off or as part of your CI process.
58
- - **Fix** vulnerabilities using `snyk wizard` and `snyk protect`.
59
- - `snyk wizard` walks you through finding and fixing known vulnerabilities in your project. Remediation options include configuring your policy file to update, auto patch and ignore vulnerabilities. (npm only)
60
- - `snyk protect` your code from vulnerabilities by applying patches and optionally suppressing specific vulnerabilities.
61
- - **Alert** `snyk monitor` records the state of dependencies and any vulnerabilities on snyk.io so you can be alerted when new vulnerabilities or updates/patches are disclosed that affect your repositories.
62
- - **Prevent** new vulnerable dependencies from being added to your project by running `snyk test` as part of your CI to fail tests when vulnerable Node.js or Ruby dependencies are added.
55
+ <details>
56
+ <summary>Standalone executables (macOS, Linux, Windows)</summary>
63
57
 
64
- ## Snyk CLI Docker images
58
+ ### Standalone executables
65
59
 
66
- [See all snyk/snyk-cli images](https://hub.docker.com/r/snyk/snyk-cli)
60
+ Use [GitHub Releases](https://github.com/snyk/snyk/releases) to download a standalone executable of Snyk CLI for your platform.
67
61
 
68
- Snyk is also provided as a set of Docker images that carry the runtime environment of each package manager. For example, the npm image will carry all of the needed setup to run `npm install` on the currently running container. Currently there are images for npm, Ruby, Maven, Gradle and SBT.
62
+ We also provide these standalone executables on our official CDN. See [the `release.json` file](https://static.snyk.io/cli/latest/release.json) for the download links:
69
63
 
70
- The images can perform `snyk test` by default on the specified project which is mounted to the container as a read/write volume, and `snyk monitor` if the `MONITOR` environment variable is set when running the docker container. If you want an HTML report for `test` command (`--json` is appended automatically). An HTML file called `snyk_report.html` and a CSS file called `snyk_report.css` will be generated. The image also writes a file called `snyk-res.json` for internal use and `snyk-error.log` for errors that we can look at if something goes wrong.
64
+ ```http
65
+ https://static.snyk.io/cli/latest/release.json
71
66
 
72
- The following environment variables can be used when running the container on docker:
67
+ # Or for specific version or platform
68
+ https://static.snyk.io/cli/v1.666.0/release.json
69
+ https://static.snyk.io/cli/latest/snyk-macos
70
+ ```
73
71
 
74
- - `SNYK_TOKEN` - Snyk API token, obtained from [https://app.snyk.io/account](https://app.snyk.io/account).
75
- - `USER_ID` - [OPTIONAL] Current user ID on the host machine. If not provided will take the user ID of the currently running user inside the container. This is used for CI builds such as Jenkins where we are running with a non-privileged user and want to allow the user to access the mounted project folder.
76
- - `MONITOR` - [OPTIONAL] If set, will generate an html report via `snyk-to-html` and runs `snyk monitor` after running `snyk test`.
77
- - `PROJECT_FOLDER` - [OPTIONAL] If set, this will cd to the directory inside the mounted project dir to run snyk inside it.
78
- - `ENV_FLAGS` - [OPTIONAL] additional environment parameters to pass to `snyk test` when running the container.
79
- - `TARGET_FILE` - [OPTIONAL] additional environment parameters to pass to `snyk test` & `snyk monitor` equal to `--file` option in the cli.
72
+ For example, to download and run the latest Snyk CLI on macOS, you could run:
80
73
 
81
- Docker images are tagged according to the package manager runtime they include, the package manager version and snyk version.
82
- The general format of tags is [snyk-version]-[package-manager]-[package-manager-version] or just [package-manager]-[package-manager-version] if we want to use the latest version of snyk. Please see available tags to see the available options.
74
+ ```bash
75
+ curl https://static.snyk.io/cli/latest/snyk-macos -o snyk
76
+ chmod +x ./snyk
77
+ mv ./snyk /usr/local/bin/
78
+ ```
83
79
 
84
- [snyk-version] - The version of snyk that is installed in the image, if version is omitted it will use the latest version.
85
- [package-manager] - One of the available package managers (e.g: npm, mvn, gradle, etc...).
86
- [package-manager-version] - The version of the package manager that is installed inside the image.
80
+ You can also use these direct links to download the executables:
87
81
 
88
- Please see the following examples on how to run Snyk inside docker:
82
+ - macOS: https://static.snyk.io/cli/latest/snyk-macos
83
+ - Windows: https://static.snyk.io/cli/latest/snyk-win.exe
84
+ - Linux: https://static.snyk.io/cli/latest/snyk-linux
85
+ - Alpine: https://static.snyk.io/cli/latest/snyk-alpine
89
86
 
90
- ### Node.js (npm)
87
+ Drawback of this method is, that you will have to manually keep the Snyk CLI up to date.
91
88
 
92
- [See all snyk/snyk-cli npm images](https://hub.docker.com/r/snyk/snyk-cli/tags?page=1&name=npm)
89
+ </details>
93
90
 
94
- The host project folder will be mounted to `/project` on the container and will be used to read the dependencies file and write results for CI builds.
91
+ <details>
92
+ <summary>Install with Homebrew (macOS, Linux)</summary>
95
93
 
96
- Here's an example of running `snyk test` and `snyk monitor` in the image (with the latest version of Snyk) for npm:
94
+ ### Homebrew
97
95
 
98
- ```
99
- docker run -it
100
- -e "SNYK_TOKEN=<TOKEN>"
101
- -e "USER_ID=1234"
102
- -e "MONITOR=true"
103
- -v "<PROJECT_DIRECTORY>:/project"
104
- snyk/snyk-cli:npm test --org=my-org-name
96
+ Install Snyk CLI from [Snyk tap](https://github.com/snyk/homebrew-tap) with [Homebrew](https://brew.sh) by running:
97
+
98
+ ```bash
99
+ brew tap snyk/tap
100
+ brew install snyk
105
101
  ```
106
102
 
107
- ### RubyGems
103
+ </details>
108
104
 
109
- [See all snyk/snyk-cli rubygems images](https://hub.docker.com/r/snyk/snyk-cli/tags?page=1&name=rubygems)
105
+ <details>
106
+ <summary>Scoop (Windows)</summary>
110
107
 
111
- The host project folder will be mounted to `/project` on the container and will be used to read the dependencies file and write results for CI builds.
108
+ ### Scoop
112
109
 
113
- Here's an example of running `snyk test` and `snyk monitor` in the image (with the latest version of Snyk) for RubyGems:
110
+ Install Snyk CLI from our [Snyk bucket](https://github.com/snyk/scoop-snyk) with [Scoop](https://scoop.sh) on Windows:
114
111
 
115
112
  ```
116
- docker run -it
117
- -e "SNYK_TOKEN=<TOKEN>"
118
- -e "USER_ID=1234"
119
- -e "MONITOR=true"
120
- -v "<PROJECT_DIRECTORY>:/project"
121
- snyk/snyk-cli:rubygems test --org=my-org-name
113
+ scoop bucket add snyk https://github.com/snyk/scoop-snyk
114
+ scoop install snyk
122
115
  ```
123
116
 
124
- ### Maven 3.5.4
117
+ </details>
125
118
 
126
- [See all snyk/snyk-cli maven images](https://hub.docker.com/r/snyk/snyk-cli/tags?page=1&name=maven)
119
+ <details>
120
+ <summary>Snyk CLI in a Docker image</summary>
127
121
 
128
- The host project folder will be mounted to `/project` on the container and will be used to read the dependencies file and write results for CI builds.
129
- You may also need to mount the local `.m2` and `.ivy2` folders.
122
+ ### Snyk CLI in a Docker image
130
123
 
131
- Here's an example of running `snyk test` and `snyk monitor` in the image (with the latest version of Snyk) for Maven:
124
+ Snyk CLI can also be run from a Docker image. Snyk offers multiple Docker images under [snyk/snyk-cli](https://hub.docker.com/r/snyk/snyk-cli) and [snyk/snyk](https://hub.docker.com/r/snyk/snyk) ([snyk/images on GitHub](https://github.com/snyk/snyk-images) for more details).
132
125
 
133
- ```
126
+ These images wrap the Snyk CLI and depending on the Tag come with a relevant tooling for different projects. For example scanning a Gradle project with snyk/snyk-cli:
127
+
128
+ ```bash
134
129
  docker run -it
135
130
  -e "SNYK_TOKEN=<TOKEN>"
136
131
  -e "USER_ID=1234"
137
- -e "MONITOR=true"
138
132
  -v "<PROJECT_DIRECTORY>:/project"
139
- -v "/home/user/.m2:/home/node/.m2"
140
- -v "/home/user/.ivy2:/home/node/.ivy2"
141
- snyk/snyk-cli:maven-3.5.4 test --org=my-org-name
133
+ -v "/home/user/.gradle:/home/node/.gradle"
134
+ snyk/snyk-cli:gradle-5.4 test --org=my-org-name
142
135
  ```
143
136
 
144
- ### SBT 0.13.16 / SBT 1.0.4
137
+ </details>
145
138
 
146
- [See all snyk/snyk-cli sbt images](https://hub.docker.com/r/snyk/snyk-cli/tags?page=1&name=sbt)
139
+ ## Install as a part of a Snyk CLI integration
147
140
 
148
- The host project folder will be mounted to `/project` on the container and will be used to read the dependencies file and write results for CI builds.
149
- You may also need to mount the local `.m2` and `.ivy2` folders.
141
+ Snyk also offers many integrations into developer tooling. These integrations will install and manage the Snyk CLI for you. For example:
150
142
 
151
- Here are examples of running `snyk test` and `snyk monitor` in the image (with the latest version of Snyk) for SBT:
143
+ - [Snyk Jenkins plugin](https://github.com/jenkinsci/snyk-security-scanner-plugin)
144
+ - [CircleCI Orb](https://github.com/snyk/snyk-orb)
145
+ - [Azure Pipelines Task](https://github.com/snyk/snyk-azure-pipelines-task)
146
+ - [GitHub Actions](https://github.com/snyk/actions)
147
+ - [IntelliJ IDE Plugin](https://github.com/snyk/snyk-intellij-plugin)
148
+ - [VS Code Extension](https://marketplace.visualstudio.com/items?itemName=snyk-security.snyk-vulnerability-scanner)
149
+ - [Eclipse IDE Extension](https://github.com/snyk/snyk-eclipse-plugin)
150
+ - [Maven plugin](https://github.com/snyk/snyk-maven-plugin)
151
+ - And many more. See [the Integrations documentation](https://support.snyk.io/hc/en-us/categories/360000598398-Integrations)
152
152
 
153
- _Note_: the `dependency-tree` or `sbt-dependency-graph` or `sbt-coursier` (included by default in latest sbt versions) module is required for `snyk` to process Scala projects.
153
+ <p align="center">
154
+ <a href="https://support.snyk.io/hc/en-us/categories/360000598398-Integrations">
155
+ <img src="help/ide.svg" alt="Snyk CLI IDE integration" width="50%" />
156
+ </a>
157
+ </p>
154
158
 
155
- ```
156
- docker run -it
157
- -e "SNYK_TOKEN=<TOKEN>"
158
- -e "USER_ID=1234"
159
- -e "MONITOR=true"
160
- -v "<PROJECT_DIRECTORY>:/project"
161
- -v "/home/user/.m2:/home/node/.m2"
162
- -v "/home/user/.ivy2:/home/node/.ivy2"
163
- snyk/snyk-cli:sbt-0.13.16 test --org=my-org-name
164
- ```
159
+ ---
165
160
 
166
- ```
167
- docker run -it
168
- -e "SNYK_TOKEN=<TOKEN>"
169
- -e "USER_ID=1234"
170
- -e "MONITOR=true"
171
- -v "<PROJECT_DIRECTORY>:/project"
172
- -v "/home/user/.m2:/home/node/.m2"
173
- -v "/home/user/.ivy2:/home/node/.ivy2"
174
- snyk/snyk-cli:sbt-1.0.4 test --org=my-org-name
175
- ```
161
+ # Getting started with Snyk CLI
176
162
 
177
- ### Gradle 2.8 / Gradle 4.4 / Gradle 5.4
163
+ Once you installed the Snyk CLI, you can verify it's working by running
178
164
 
179
- [See all snyk/snyk-cli gradle images](https://hub.docker.com/r/snyk/snyk-cli/tags?page=1&name=gradle)
165
+ ```bash
166
+ snyk --version
167
+ ```
180
168
 
181
- The host project folder will be mounted to `/project` on the container and will be used to read the dependencies file and write results for CI builds.
182
- You may also need to mount the local `.gradle`.
169
+ ## Authorization
183
170
 
184
- Here's an example of running `snyk test` and `snyk monitor` in the image (with the latest version of Snyk) for Gradle:
171
+ Snyk CLI depends on [Snyk.io](https://snyk.io) APIs. Connect your Snyk CLI with [Snyk.io](https://snyk.io) by running:
185
172
 
173
+ ```bash
174
+ snyk auth
186
175
  ```
187
- docker run -it
188
- -e "SNYK_TOKEN=<TOKEN>"
189
- -e "USER_ID=1234"
190
- -e "MONITOR=true"
191
- -v "<PROJECT_DIRECTORY>:/project"
192
- -v "/home/user/.gradle:/home/node/.gradle"
193
- snyk/snyk-cli:gradle-2.8 test --org=my-org-name
176
+
177
+ ## Scanning your project
178
+
179
+ If you are already in a folder with a supported project, start by running:
180
+
181
+ ```bash
182
+ snyk test
194
183
  ```
195
184
 
185
+ Or scan a Docker image by its tag with [Snyk Container](https://snyk.io/product/container-vulnerability-management/):
186
+
187
+ ```bash
188
+ snyk container test ubuntu:18.04
196
189
  ```
197
- docker run -it
198
- -e "SNYK_TOKEN=<TOKEN>"
199
- -e "USER_ID=1234"
200
- -e "MONITOR=true"
201
- -v "<PROJECT_DIRECTORY>:/project"
202
- -v "/home/user/.gradle:/home/node/.gradle"
203
- snyk/snyk-cli:gradle-4.4 test --org=my-org-name
190
+
191
+ Or a k8s file:
192
+
193
+ ```bash
194
+ snyk iac test /path/to/kubernetes_file.yaml
204
195
  ```
205
196
 
197
+ ## Monitoring your project
198
+
199
+ Snyk can also monitor your project periodically and alert you for new vulnerabilities. The `snyk monitor` is similar to `snyk test` and can be used to create a project on the Snyk website that will be continuously monitored for new vulnerabilities.
200
+
201
+ <p align="center">
202
+ <a href="https://snyk.io">
203
+ <img src="help/monitor.svg" alt="Snyk CLI monitor projects" width="70%" />
204
+ </a>
205
+ </p>
206
+
206
207
  ```
207
- docker run -it
208
- -e "SNYK_TOKEN=<TOKEN>"
209
- -e "USER_ID=1234"
210
- -e "MONITOR=true"
211
- -v "<PROJECT_DIRECTORY>:/project"
212
- -v "/home/user/.gradle:/home/node/.gradle"
213
- snyk/snyk-cli:gradle-5.4 test --org=my-org-name
208
+ > snyk monitor
209
+ Monitoring /project (project-name)...
210
+
211
+ Explore this snapshot at https://app.snyk.io/org/my-org/project/29361c2c-9005-4692-8df4-88f1c040fa7c/history/e1c994b3-de5d-482b-9281-eab4236c851e
212
+
213
+ Notifications about newly disclosed issues related to these dependencies will be emailed to you.
214
214
  ```
215
215
 
216
- ### Docker
216
+ ### Add Snyk to your CI/CD
217
217
 
218
- [See all snyk/snyk-cli docker images](https://hub.docker.com/r/snyk/snyk-cli/tags?page=1&name=docker)
218
+ Snyk is really powerful when you are continuously scanning and monitoring your projects for vulnerabilities.
219
219
 
220
- The host project folder will be mounted to `/project` on the container and will be used to read the dependencies file and write results for CI builds.
220
+ Use one of [our integrations](#install-as-a-part-of-a-snyk-cli-integration) to stay secure.
221
221
 
222
- The image being tested is expected to be available locally.
222
+ You can authorize Snyk CLI in your CI/CD programatically:
223
223
 
224
- Here's an example of running `snyk test` and `snyk monitor` in the image (with the latest version of Snyk) for Docker:
224
+ ```bash
225
+ # Using a SNYK_TOKEN envvar (preferred)
226
+ SNYK_TOKEN=<SNYK_API_TOKEN> snyk test
225
227
 
226
- ```
227
- docker run -it
228
- -e "SNYK_TOKEN=<TOKEN>"
229
- -e "USER_ID=1234"
230
- -e "MONITOR=true"
231
- -v "<PROJECT_DIRECTORY>:/project"
232
- -v "/var/run/docker.sock:/var/run/docker.sock"
233
- snyk/snyk-cli:docker test --docker myapp:mytag --file=<DOCKERFILE>
228
+ # Or using a Snyk auth command
229
+ snyk auth <SNYK_API_TOKEN>
230
+ snyk test
234
231
  ```
235
232
 
236
- ### Python 2 / Python 3
233
+ ## More flags and options to try
237
234
 
238
- [See all snyk/snyk-cli python images](https://hub.docker.com/r/snyk/snyk-cli/tags?page=1&name=python)
235
+ Here are some flags that you might find useful:
239
236
 
240
- The host project folder will be mounted to `/project` on the container and will be used to read the dependencies file and write results for CI builds.
237
+ - `--severity-threshold=low|medium|high|critical`
241
238
 
242
- Here's an example of running `snyk test` and `snyk monitor` in the image (with the latest version of Snyk) for Maven:
239
+ Only report vulnerabilities of provided level or higher.
243
240
 
244
- - _setup.py_
241
+ - `--json`
245
242
 
246
- ```
247
- docker run -it
248
- -e "SNYK_TOKEN=<TOKEN>"
249
- -e "USER_ID=1234"
250
- -e "MONITOR=true"
251
- -e "TARGET_FILE=setup.py"
252
- -v "<PROJECT_DIRECTORY>:/project"
253
- snyk/snyk-cli:python-3 test --org=my-org-name
254
- ```
243
+ Prints results in JSON format.
255
244
 
256
- - _Pipfile_
245
+ - `--all-projects`
257
246
 
258
- ```
259
- docker run -it
260
- -e "SNYK_TOKEN=<TOKEN>"
261
- -e "USER_ID=1234"
262
- -e "MONITOR=true"
263
- -e "TARGET_FILE=Pipfile"
264
- -v "<PROJECT_DIRECTORY>:/project"
265
- snyk/snyk-cli:python-3 test --org=my-org-name
266
- ```
247
+ Auto-detect all projects in working directory
267
248
 
268
- - _requirements.txt_
249
+ See all the available commands and options by running `--help`:
269
250
 
270
- ```
271
- docker run -it
272
- -e "SNYK_TOKEN=<TOKEN>"
273
- -e "USER_ID=1234"
274
- -e "MONITOR=true"
275
- -e "TARGET_FILE=requirement-dev.txt"
276
- -v "<PROJECT_DIRECTORY>:/project"
277
- snyk/snyk-cli:python-3 test --org=my-org-name
251
+ ```bash
252
+ snyk --help
253
+ # or get help for a specific command like
254
+ snyk iac --help
255
+ snyk code --help
278
256
  ```
279
257
 
280
- ## Badge
258
+ # Getting support
281
259
 
282
- Make users feel more confident in using your website by adding your Snyk badge!
260
+ We recommend reaching out via the [support@snyk.io](mailto:support@snyk.io) email whenever you need help with Snyk CLI or Snyk in general.
283
261
 
284
- <a href="https://snyk.io/test/github/snyk/snyk"><img src="https://snyk.io/test/github/snyk/snyk/badge.svg" alt="Known Vulnerabilities"/></a>
262
+ GitHub Issues on any [Snyk project](https://github.com/snyk) are not actively monitored by Snyk support.
285
263
 
286
- ```
287
- [![Known Vulnerabilities](https://snyk.io/package/npm/snyk/badge.svg)](https://snyk.io/package/npm/snyk)
288
- ```
264
+ ## Contributing
265
+
266
+ This project is open source but we don't encourage outside contributors.
267
+
268
+ This repository is a monorepo, also covering other projects and tools:
269
+
270
+ - [`@snyk/protect`](packages/snyk-protect): [npm package for `snyk-protect` command](https://www.npmjs.com/package/@snyk/protect)
271
+
272
+ ## Security
273
+
274
+ For any security issues or concerns, please see [SECURITY.md](SECURITY.md) file in this repository.
289
275
 
290
- [![Analytics](https://ga-beacon.appspot.com/UA-69111857-2/Snyk/snyk?pixel)](https://snyk.io/)
276
+ Made with 💜 by Snyk