snyk 1.913.0 → 1.916.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
@@ -61,7 +61,7 @@ Use [GitHub Releases](https://github.com/snyk/snyk/releases) to download a stand
61
61
 
62
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:
63
63
 
64
- ```http
64
+ ```text
65
65
  https://static.snyk.io/cli/latest/release.json
66
66
 
67
67
  # Or for specific version or platform
@@ -87,6 +87,44 @@ You can also use these direct links to download the executables:
87
87
 
88
88
  Drawback of this method is, that you will have to manually keep the Snyk CLI up to date.
89
89
 
90
+ #### Verifying standalone binaries
91
+
92
+ You can verify both shasum of downloaded binaries and their GPG signatures.
93
+
94
+ Download location on `static.snyk.io` contains a file called `sha256sums.txt.asc`.
95
+ You can download it directly `https://static.snyk.io/cli/latest/sha256sums.txt.asc` or for a specific version like `https://static.snyk.io/cli/v1.666.0/sha256sums.txt.asc`.
96
+
97
+ To check that a downloaded file matches the checksum, use a `sha256sum` command like so:
98
+
99
+ ```bash
100
+ grep snyk-macos sha256sums.txt.asc | sha256sum -c -
101
+ ```
102
+
103
+ If you want to verify Snyk CLI standalone binaries against [Snyk CLI GPG key](help/_about-this-project/snyk-code-signing-public.pgp), you will need to import it first:
104
+
105
+ ```bash
106
+ # 68BFBCCEB7794E6FC06A2044A29C32E91F4B9569 is the key belonging to code-signing@snyk.io
107
+ # Copy of this public key is also in this repository /help/_about-this-project/snyk-code-signing-public.pgp
108
+ gpg --keyserver hkps://keys.openpgp.org --recv-keys 68BFBCCEB7794E6FC06A2044A29C32E91F4B9569
109
+ ```
110
+
111
+ Then verify the file is signed with:
112
+
113
+ ```bash
114
+ gpg --verify sha256sums.txt.asc
115
+ ```
116
+
117
+ Command output should look like:
118
+
119
+ ```plain
120
+ gpg: Signature made Mon Apr 25 16:55:01 2022 CEST
121
+ gpg: using RSA key 68BFBCCEB7794E6FC06A2044A29C32E91F4B9569
122
+ gpg: Good signature from "Snyk Limited <code-signing@snyk.io>" [unknown]
123
+ gpg: WARNING: This key is not certified with a trusted signature!
124
+ gpg: There is no indication that the signature belongs to the owner.
125
+ Primary key fingerprint: 68BF BCCE B779 4E6F C06A 2044 A29C 32E9 1F4B 9569
126
+ ```
127
+
90
128
  </details>
91
129
 
92
130
  <details>
@@ -4,7 +4,6 @@
4
4
  "devDeps": false,
5
5
  "PRUNE_DEPS_THRESHOLD": 40000,
6
6
  "MAX_PATH_COUNT": 1500000,
7
- "CODE_CLIENT_PROXY_URL": "https://deeproxy.snyk.io",
8
7
  "NPM_TREE_SIZE_LIMIT": 6.0e6,
9
8
  "YARN_TREE_SIZE_LIMIT": 6.0e6
10
9
  }
@@ -177773,6 +177773,8 @@ function inspect(root, targetFile, options) {
177773
177773
  const mvnArgs = buildArgs(root, mvnWorkingDirectory, targetFile, options.args);
177774
177774
  let result;
177775
177775
  try {
177776
+ debug(`Maven command: ${mavenCommand} ${mvnArgs.join(' ')}`);
177777
+ debug(`Maven working directory: ${mvnWorkingDirectory}`);
177776
177778
  result = yield subProcess.execute(mavenCommand, mvnArgs, {
177777
177779
  cwd: mvnWorkingDirectory,
177778
177780
  });