snyk 1.1286.0 → 1.1286.1

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.
Files changed (13) hide show
  1. package/help/cli-commands/code-test.md +5 -1
  2. package/help/cli-commands/container-monitor.md +4 -2
  3. package/help/cli-commands/container-sbom.md +7 -7
  4. package/help/cli-commands/container-test.md +5 -1
  5. package/help/cli-commands/iac-test.md +5 -1
  6. package/help/cli-commands/monitor.md +3 -1
  7. package/help/cli-commands/sbom.md +8 -8
  8. package/help/cli-commands/test.md +2 -0
  9. package/package.json +1 -1
  10. package/src/generated/sha256sums.txt +8 -8
  11. package/src/generated/version +1 -1
  12. package/wrapper_dist/generated/sha256sums.txt +8 -8
  13. package/wrapper_dist/generated/version +1 -1
package/help/cli-commands/code-test.md CHANGED
@@ -37,7 +37,11 @@ Set a default to ensure all newly tested projects are tested under your default
37
37
 
38
38
  Default: `<ORG_ID>` that is the current preferred Organization in your [Account settings](https://app.snyk.io/account)
39
39
 
40
- Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
40
+ **Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
41
+
42
+ `orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://snyk.io/org/[orgslugname]`. The orgname does not work.
43
+
44
+ For more information see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli)
41
45
 
42
46
  ### `--report`
43
47
 
package/help/cli-commands/container-monitor.md CHANGED
@@ -46,9 +46,11 @@ Set a default to ensure all newly tested and monitored projects are tested and m
46
46
 
47
47
  Default: `<ORG_ID>` that is the current preferred Organization in your [Account settings](https://app.snyk.io/account)
48
48
 
49
- Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
49
+ **Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
50
50
 
51
- For more information see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/test-for-vulnerabilities/how-to-select-the-organization-to-use-in-the-cli)
51
+ `orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://snyk.io/org/[orgslugname]`. The orgname does not work.
52
+
53
+ For more information see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli)
52
54
 
53
55
  ### `--file=<FILE_PATH>`
54
56
 
package/help/cli-commands/container-sbom.md CHANGED
@@ -10,13 +10,13 @@ The `snyk container sbom` feature requires an internet connection.
10
10
 
11
11
  ## Usage
12
12
 
13
- `$ snyk container sbom --format=<cyclonedx1.4+json|cyclonedx1.4+xml|spdx2.3+json> [--org=<ORG_ID>] [--exclude-app-vulns] <IMAGE>`
13
+ `$ snyk container sbom --format=<cyclonedx1.4+json|cyclonedx1.4+xml|cyclonedx1.5+json|cyclonedx1.5+xml|spdx2.3+json> [--org=<ORG_ID>] [--exclude-app-vulns] <IMAGE>`
14
14
 
15
15
  ## Description
16
16
 
17
17
  The `snyk container sbom` command generates an SBOM for a container image.
18
18
 
19
- Supported formats include CycloneDX v1.4 (JSON or XML) and SPDX v2.3 (JSON).
19
+ Supported formats include CycloneDX v1.4 (JSON or XML), CycloneDX v1.5 (JSON or XML) and SPDX v2.3 (JSON).
20
20
 
21
21
  An SBOM can be generated for operating system dependencies as well as application dependencies within the image. Unmanaged dependencies are currently not supported.
22
22
 
@@ -33,11 +33,11 @@ Use the `-d` or `--debug` option to output the debug logs.
33
33
 
34
34
  ## Options
35
35
 
36
- ### `--format=<cyclonedx1.4+json|cyclonedx1.4+xml|spdx2.3+json>`
36
+ ### `--format=<cyclonedx1.4+json|cyclonedx1.4+xml|cyclonedx1.5+json|cyclonedx1.5+xml|spdx2.3+json>`
37
37
 
38
38
  Required. Specify the output format for the SBOM to be produced.
39
39
 
40
- Set the desired SBOM output format. Available options are `cyclonedx1.4+json`, `cyclonedx1.4+xml`, and `spdx2.3+json`
40
+ Set the desired SBOM output format. Available options are `cyclonedx1.4+json`, `cyclonedx1.4+xml`, `cyclonedx1.5+json`, `cyclonedx1.5+xml` and `spdx2.3+json`
41
41
 
42
42
  ### `[--org=<ORG_ID>]`
43
43
 
@@ -77,11 +77,11 @@ Required. The image for which you will generate an SBOM document.
77
77
 
78
78
  ### Create a CycloneDX JSON document for an image
79
79
 
80
- `$ snyk container sbom --format=cyclonedx1.4+json redis:latest`
80
+ `$ snyk container sbom --format=cyclonedx1.5+json redis:latest`
81
81
 
82
82
  ### Create a CycloneDX JSON document for an image and redirect stdout to a file
83
83
 
84
- `$ snyk container sbom --format=cyclonedx1.4+json redis:latest > mySBOM.json`
84
+ `$ snyk container sbom --format=cyclonedx1.5+json redis:latest > mySBOM.json`
85
85
 
86
86
  ### Create a SPDX JSON document for an image while excluding application dependencies
87
87
 
@@ -89,4 +89,4 @@ Required. The image for which you will generate an SBOM document.
89
89
 
90
90
  ### Refer to a container image by its digest
91
91
 
92
- `$ snyk container sbom --format=cyclonedx1.4+xml alpine@sha256:c5c5fda71656f28e49ac9c5416b3643eaa6a108a8093151d6d1afc9463be8e33`
92
+ `$ snyk container sbom --format=cyclonedx1.5+xml alpine@sha256:c5c5fda71656f28e49ac9c5416b3643eaa6a108a8093151d6d1afc9463be8e33`
package/help/cli-commands/container-test.md CHANGED
@@ -45,7 +45,11 @@ Set a default to ensure all newly tested and monitored projects are tested and m
45
45
 
46
46
  Default: `<ORG_ID>` that is the current preferred Organization in your [Account settings](https://app.snyk.io/account)
47
47
 
48
- Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
48
+ **Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
49
+
50
+ `orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://snyk.io/org/[orgslugname]`. The orgname does not work.
51
+
52
+ For more information see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli)
49
53
 
50
54
  ### `--file=<FILE_PATH>`
51
55
 
package/help/cli-commands/iac-test.md CHANGED
@@ -51,7 +51,11 @@ Set a default to ensure all newly tested projects are tested under your default
51
51
 
52
52
  Default: `<ORG_ID>` that is the current preferred Organization in your [Account settings](https://app.snyk.io/account)
53
53
 
54
- Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
54
+ **Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
55
+
56
+ `orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://snyk.io/org/[orgslugname]`. The orgname does not work.
57
+
58
+ For more information see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli)
55
59
 
56
60
  ### `--ignore-policy`
57
61
 
package/help/cli-commands/monitor.md CHANGED
@@ -121,7 +121,9 @@ Set a default to ensure all newly monitored projects are created under your defa
121
121
 
122
122
  Default: `<ORG_ID>` that is the current preferred Organization in your [Account settings](https://app.snyk.io/account)
123
123
 
124
- Note that you can also use `--org=<orgslugname>`. The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
124
+ **Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
125
+
126
+ `orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://snyk.io/org/[orgslugname]`. The orgname does not work.
125
127
 
126
128
  For more information see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli)
127
129
 
package/help/cli-commands/sbom.md CHANGED
@@ -10,13 +10,13 @@ The `snyk sbom` feature requires an internet connection.
10
10
 
11
11
  ## Usage
12
12
 
13
- `$ snyk sbom --format=<cyclonedx1.4+json|cyclonedx1.4+xml|spdx2.3+json> [--file=<FILE>] [--unmanaged] [--org=<ORG_ID>] [--dev] [--all-projects] [--name=<NAME>] [--version=<VERSION>] [--exclude=<NAME>[,<NAME>...]] [--detection-depth=<DEPTH>] [--prune-repeated-subdependencies|-p] [--maven-aggregate-project] [--scan-unmanaged] [--scan-all-unmanaged] [--sub-project=<NAME>] [--gradle-sub-project=<NAME>] [--all-sub-projects] [--configuration-matching=<CONFIGURATION_REGEX>] [--configuration-attributes=<ATTRIBUTE>[,<ATTRIBUTE>]] [--init-script=<FILE>] [--json-file-output=<OUTPUT_FILE_PATH>] [<TARGET_DIRECTORY>]`
13
+ `$ snyk sbom --format=<cyclonedx1.4+json|cyclonedx1.4+xml|cyclonedx1.5+json|cyclonedx1.5+xml|spdx2.3+json> [--file=<FILE>] [--unmanaged] [--org=<ORG_ID>] [--dev] [--all-projects] [--name=<NAME>] [--version=<VERSION>] [--exclude=<NAME>[,<NAME>...]] [--detection-depth=<DEPTH>] [--prune-repeated-subdependencies|-p] [--maven-aggregate-project] [--scan-unmanaged] [--scan-all-unmanaged] [--sub-project=<NAME>] [--gradle-sub-project=<NAME>] [--all-sub-projects] [--configuration-matching=<CONFIGURATION_REGEX>] [--configuration-attributes=<ATTRIBUTE>[,<ATTRIBUTE>]] [--init-script=<FILE>] [--json-file-output=<OUTPUT_FILE_PATH>] [<TARGET_DIRECTORY>]`
14
14
 
15
15
  ## Description
16
16
 
17
17
  The `snyk sbom` command generates an SBOM for a local software project in an ecosystem supported by Snyk.
18
18
 
19
- Supported formats include CycloneDX v1.4 (JSON or XML) and SPDX v2.3 (JSON).
19
+ Supported formats include CycloneDX v1.4 (JSON or XML), CycloneDX v1.5 (JSON or XML) and SPDX v2.3 (JSON).
20
20
 
21
21
  An SBOM can be generated for all supported Open Source package managers as well as unmanaged software projects.
22
22
 
@@ -33,11 +33,11 @@ Use the `-d` or `--debug` option to output the debug logs.
33
33
 
34
34
  ## Options
35
35
 
36
- ### `--format=<cyclonedx1.4+json|cyclonedx1.4+xml|spdx2.3+json>`
36
+ ### `--format=<cyclonedx1.4+json|cyclonedx1.4+xml|cyclonedx1.5+json|cyclonedx1.5+xml|spdx2.3+json>`
37
37
 
38
38
  Required. Specify the output format for the SBOM to be produced.
39
39
 
40
- Set the desired SBOM output format. Available options are `cyclonedx1.4+json`, `cyclonedx1.4+xml`, and `spdx2.3+json`
40
+ Set the desired SBOM output format. Available options are `cyclonedx1.4+json`, `cyclonedx1.4+xml`, `cyclonedx1.5+json`, `cyclonedx1.5+xml` and `spdx2.3+json`
41
41
 
42
42
  ### `[--org=<ORG_ID>]`
43
43
 
@@ -288,11 +288,11 @@ Example: `snyk sbom -- -s settings.xml`
288
288
 
289
289
  ### Create a CycloneDX JSON document for a local software project
290
290
 
291
- `$ snyk sbom --format=cyclonedx1.4+json`
291
+ `$ snyk sbom --format=cyclonedx1.5+json`
292
292
 
293
293
  ### Create a CycloneDX JSON document and redirect stdout to a file
294
294
 
295
- `$ snyk sbom --format=cyclonedx1.4+json > mySBOM.json`
295
+ `$ snyk sbom --format=cyclonedx1.5+json > mySBOM.json`
296
296
 
297
297
  ### Create an SPDX JSON document and write it to a file
298
298
 
@@ -304,8 +304,8 @@ Example: `snyk sbom -- -s settings.xml`
304
304
 
305
305
  ### Create a CycloneDX XML document for a Maven project
306
306
 
307
- `$ snyk sbom --file=pom.xml --format=cyclonedx1.4+xml`
307
+ `$ snyk sbom --file=pom.xml --format=cyclonedx1.5+xml`
308
308
 
309
309
  ### Create a CycloneDX JSON document for a monorepo
310
310
 
311
- `$ snyk sbom --format=cyclonedx1.4+json --all-projects`
311
+ `$ snyk sbom --format=cyclonedx1.5+json --all-projects`
package/help/cli-commands/test.md CHANGED
@@ -114,6 +114,8 @@ Default: `<ORG_ID>` that is the current preferred Organization in your [Account
114
114
 
115
115
  **Note:** You can also use `--org=<orgslugname>.` The `ORG_ID` works in both the CLI and the API. The Organization slug name works in the CLI, but not in the API.
116
116
 
117
+ `orgslugname` must match the slug name as displayed in the URL of your org in the Snyk UI: `https://snyk.io/org/[orgslugname]`. The orgname does not work.
118
+
117
119
  For more information see the article [How to select the Organization to use in the CLI](https://docs.snyk.io/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli)
118
120
 
119
121
  ### `--file=<FILE>`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "snyk",
3
- "version": "1.1286.0",
3
+ "version": "1.1286.1",
4
4
  "description": "snyk library and cli utility",
5
5
  "files": [
6
6
  "*"
package/src/generated/sha256sums.txt CHANGED
@@ -1,8 +1,8 @@
1
- d72a6ce11f76c665c7669271aee0a54bb6520156fadc2d5070394a5ecc100304 snyk-alpine
2
- 49044c595b04fe474f9b871449cd0ec7de8b7c56cf9050ab955c99066bb1bbf5 snyk-fix.tgz
3
- 2ff4f7331c5a0dbde2e8434de3bb3e056173368c7658c6d7a4cd77c9ecbda5cb snyk-linux-arm64
4
- d443857b7763825a74b57577c5c078609e57d390509bc840e9178abe0b910c87 snyk-linux
5
- cae6eced09a2961e74457b0ad5c0c1cf9e97812e3aa1a6c84e14939b3726231a snyk-macos-arm64
6
- 6db8f0db905ae06b97951099cfcbb3f7c2da945fe3fbbb69455961a44358c9c0 snyk-macos
7
- 87d14158b4d59937a09160b2768f055efe922def84420794c81cd39134f96fff snyk-protect.tgz
8
- b6e3c6c7a7d74bc09e7bfffdd5d58a472afb51bc3979727405757d7e6e515b58 snyk-win.exe
1
+ 45cb5312e305f40deed025514053ad5c8306187ccdb546d0968def32dc2cabc0 snyk-alpine
2
+ dc15d21aa642ba0372c9a2538f4a9d488f9779c3f095b71bb8d0583e15c05049 snyk-fix.tgz
3
+ 20b0d93c7fdff7162142cf02d82f067d702649fd364f760b15d11658fa98f05d snyk-linux-arm64
4
+ 0bc957445408ebfc92535f8f6617ab7e0f34fc6e8c37985969b403ba0b55b4e3 snyk-linux
5
+ d0d0db1bd1462bfd99f33409ed498274e7f450715828c54b113ab33f65e0bd1b snyk-macos-arm64
6
+ 5413591ee90379ad23acb3f7726bfe43885dd20170c5178808257466b4e73239 snyk-macos
7
+ b0b38d13da715fcd6f78c0cf81d4c5063a1fc60495fdd44169355e1ca15b1593 snyk-protect.tgz
8
+ 2469f1a83ddc3b233a9d539ab472b71bc87ede48cb90186424ddc7178fbf784b snyk-win.exe
package/src/generated/version CHANGED
@@ -1 +1 @@
1
- 1.1286.0
1
+ 1.1286.1
package/wrapper_dist/generated/sha256sums.txt CHANGED
@@ -1,8 +1,8 @@
1
- d72a6ce11f76c665c7669271aee0a54bb6520156fadc2d5070394a5ecc100304 snyk-alpine
2
- 49044c595b04fe474f9b871449cd0ec7de8b7c56cf9050ab955c99066bb1bbf5 snyk-fix.tgz
3
- 2ff4f7331c5a0dbde2e8434de3bb3e056173368c7658c6d7a4cd77c9ecbda5cb snyk-linux-arm64
4
- d443857b7763825a74b57577c5c078609e57d390509bc840e9178abe0b910c87 snyk-linux
5
- cae6eced09a2961e74457b0ad5c0c1cf9e97812e3aa1a6c84e14939b3726231a snyk-macos-arm64
6
- 6db8f0db905ae06b97951099cfcbb3f7c2da945fe3fbbb69455961a44358c9c0 snyk-macos
7
- 87d14158b4d59937a09160b2768f055efe922def84420794c81cd39134f96fff snyk-protect.tgz
8
- b6e3c6c7a7d74bc09e7bfffdd5d58a472afb51bc3979727405757d7e6e515b58 snyk-win.exe
1
+ 45cb5312e305f40deed025514053ad5c8306187ccdb546d0968def32dc2cabc0 snyk-alpine
2
+ dc15d21aa642ba0372c9a2538f4a9d488f9779c3f095b71bb8d0583e15c05049 snyk-fix.tgz
3
+ 20b0d93c7fdff7162142cf02d82f067d702649fd364f760b15d11658fa98f05d snyk-linux-arm64
4
+ 0bc957445408ebfc92535f8f6617ab7e0f34fc6e8c37985969b403ba0b55b4e3 snyk-linux
5
+ d0d0db1bd1462bfd99f33409ed498274e7f450715828c54b113ab33f65e0bd1b snyk-macos-arm64
6
+ 5413591ee90379ad23acb3f7726bfe43885dd20170c5178808257466b4e73239 snyk-macos
7
+ b0b38d13da715fcd6f78c0cf81d4c5063a1fc60495fdd44169355e1ca15b1593 snyk-protect.tgz
8
+ 2469f1a83ddc3b233a9d539ab472b71bc87ede48cb90186424ddc7178fbf784b snyk-win.exe
package/wrapper_dist/generated/version CHANGED
@@ -1 +1 @@
1
- 1.1286.0
1
+ 1.1286.1