snyk 1.1306.3 → 1.1306.4

package/dist/cli/thirdPartyNotice.json

@@ -1338,19 +1338,19 @@
   },
   {
     "name": "js-yaml",
-    "version": "4.3.0",
+    "version": "4.3.1",
     "author": "Vladimir Zapparov <dervus.grim@gmail.com>",
     "repository": null,
-    "source": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.3.0.tgz",
+    "source": "https://registry.npmjs.org/js-yaml/-/js-yaml-4.3.1.tgz",
     "license": "MIT",
     "licenseText": "(The MIT License)\n\nCopyright (C) 2011-2015 by Vitaly Puzrin\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n"
   },
   {
     "name": "js-yaml",
-    "version": "3.15.0",
+    "version": "3.15.1",
     "author": "Vladimir Zapparov <dervus.grim@gmail.com>",
     "repository": null,
-    "source": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.15.0.tgz",
+    "source": "https://registry.npmjs.org/js-yaml/-/js-yaml-3.15.1.tgz",
     "license": "MIT",
     "licenseText": "(The MIT License)\n\nCopyright (C) 2011-2015 by Vitaly Puzrin\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in\nall copies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN\nTHE SOFTWARE.\n"
   },

package/help/cli-commands/README.md

@@ -44,6 +44,10 @@ These commands find and report security issues in Infrastructure as Code files;
 
 The `snyk code test` command finds security issues using Static Code Analysis.
 
+### [`snyk secrets`](secrets-test.md)
+
+The `snyk secrets test` command scans text files in a repository for hardcoded secrets.
+
 ### [`snyk sbom`](sbom.md)
 
 Generate or test an SBOM document in ecosystems supported by Snyk.

package/help/cli-commands/ignore-create.md

@@ -0,0 +1,83 @@
+---
+description: The snyk ignore create command that creates a Snyk Code ignore
+hidden: true
+noIndex: true
+---
+
+# Ignore create
+
+## Usage and description
+
+`snyk ignore create --finding-id=<FINDING_ID> --ignore-type=<not-vulnerable|wont-fix|temporary-ignore> --reason=<REASON> --expiration=<YYYY-MM-DD|never> [--org=<ORG_ID>] [--remote-repo-url=<URL>] [OPTIONS]`
+
+The `snyk ignore create` command creates an ignore for a Snyk Code finding using Consistent Ignores for Snyk Code. Snyk stores the ignore on the finding and applies it consistently across the CLI, IDE, and other integrations on the next test.
+
+**Note:** This command applies only to Snyk Code. To ignore Snyk Open Source or Snyk IaC issues, use the [`snyk ignore`](ignore.md) command without the `create` subcommand.
+
+Creating ignores from the command line is an Early Access feature of the Ignore Approval Workflow. It applies to `snyk code test` runs from the CLI and IDE. It does not apply to SCM (stateful) tests run through the Import API, and it does not support CLI Upload projects.
+
+## Prerequisites
+
+Complete the following before you create an ignore:
+
+- Install Snyk CLI v1.1297.1 or later. Visit [Install or update the Snyk CLI](https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli).
+- Enable Consistent Ignores for Snyk Code for your Group or Organization. Visit [Consistent Ignores for Snyk Code](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code).
+- Set the Organization that holds the ignores. Visit [How to select the Organization to use in the CLI](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/how-to-select-the-organization-to-use-in-the-cli).
+- Commit and push your code to the remote repository so that reviewers can locate the finding.
+
+This command identifies a finding by its finding identifier. To obtain it, run `snyk code test --json` and locate `runs.results[n].fingerprints.snyk/assets/finding/v1` in the output. Visit [Consistent Ignores for Snyk Code CLI](https://docs.snyk.io/scan-fix-and-prevent/fix/prioritize-issues-for-fixing/ignore-issues/consistent-ignores-for-snyk-code/snyk-cli#access-the-finding-identifier-in-json-and-sarif-output).
+
+## Interactive and non-interactive modes
+
+By default, `snyk ignore create` runs interactively and prompts for each value. Run the command without options to use interactive mode.
+
+To run non-interactively, for example in a script or CI/CD pipeline, provide all required options.
+
+## Options
+
+### `--finding-id=<FINDING_ID>`
+
+Finding to ignore. Required.
+
+Obtain the finding identifier from the JSON output of `snyk code test --json`.
+
+### `--ignore-type=<not-vulnerable|wont-fix|temporary-ignore>`
+
+Reason category for the ignore. Required.
+
+### `--reason=<REASON>`
+
+Human-readable justification for the ignore. Required and must not be empty.
+
+### `--expiration=<YYYY-MM-DD|never>`
+
+Expiration date in `YYYY-MM-DD` format, or `never`. Required in non-interactive mode.
+
+### `--org=<ORG_ID>`
+
+Organization that holds the ignore. The value must be a valid Organization ID.
+
+Default: the Organization set in your CLI configuration
+
+### `--remote-repo-url=<URL>`
+
+Repository URL for the finding. Snyk detects this automatically when a .git directory is present. Specify it explicitly when the repository has a different Git URL. To verify the URL, run `git remote -v`.
+
+## Examples for the `snyk ignore create` command
+
+### Create an ignore interactively
+
+```
+$ snyk ignore create
+```
+
+### Create an ignore non-interactively
+
+```
+$ snyk ignore create \
+  --finding-id=<FINDING_ID> \
+  --ignore-type=wont-fix \
+  --reason="Not exploitable in this context" \
+  --expiration=2026-12-31 \
+  --org=<ORG_ID>
+```

package/help/cli-commands/ignore.md

@@ -8,7 +8,7 @@
 
 The `snyk ignore` command modifies the `.snyk` policy file to ignore a specified issue according to its Snyk ID for all occurrences, its expiry date, a reason, or according to paths in the filesystem for the policy, the issue, or both.
 
-**Note:** Ignoring issues or vulnerabilities using the `.snyk` file is not supported for Snyk Code.
+**Note:** Ignoring issues or vulnerabilities using the `.snyk` file is not supported for Snyk Code. To ignore a Snyk Code finding from the command line, use the [`snyk ignore create`](ignore-create.md) command with Consistent Ignores for Snyk Code.
 
 ### Exclude
 

package/help/cli-commands/secrets-test.md

@@ -0,0 +1,95 @@
+# Secrets test
+
+## Prerequisites
+
+To use the `snyk secrets test` command:
+
+- Install the latest version of the [Snyk CLI](../install-the-snyk-cli/)
+- [Authenticate](auth.md) your machine with the Snyk CLI using `snyk auth`.
+- Ensure the Secrets feature is enabled for your Organization. If you receive a `SNYK-CLI-0016` error, contact your Snyk account manager.
+
+## Usage
+
+`snyk secrets test [PATH]`
+
+## Description
+
+Scan your source code to identify and manage sensitive information such as API keys, passwords, and tokens. This command finds hardcoded secrets in your current directory or a specified path. The command always scans the targeted directory recursively.
+
+## Exit codes
+
+**0**: Success. No secrets found, or all found secrets are ignored.\
+**1**: Action needed. Secrets found require attention.\
+**2**: Failure. An error occurred.
+
+## Debug
+
+Use the `-d` option to output the debug logs.
+
+## Options
+
+### `--exclude=<NAME>[,<NAME>]...`
+
+Exclude directory names and file names from the scan. Provide a comma-separated list of names. Do not include a path. Example: `snyk secrets test --exclude=dir1,file2` This excludes any directories and files named `dir1` and `file2` from the secrets scan, such as `./dir1`, `./src/dir1`, `./file2`, and `./src/file2`.
+
+### `--org=<ORG_ID>`
+
+Specify the Snyk Organization to associate the test results with. Example: `snyk secrets test --org=<ORG_ID>`
+
+### `--include-ignores`
+
+Include ignored findings in the scan results. Use this option to audit your codebase and review suppressed items. Example: `snyk secrets test --include-ignores`
+
+### `--severity-threshold=<low|medium|high|critical>`
+
+Report only vulnerabilities at the specified level or higher. Allowed values: `low`, `medium`, `high`, `critical`.
+
+### `--report`
+
+Share results with the Snyk Web UI. This creates a project in your Snyk account with a snapshot of the current issues or appends the snapshot to an existing project. After using this option, log in to the Snyk website and view your projects to see the snapshot. When you use `--report`, enable the **View Project Ignores** permission for the service account or user token. Snyk requires this permission to access ignore information when you report results. If Snyk returns a `403 Forbidden` error, ensure your service account role includes this permission. Example: `snyk secrets test --report`
+
+### `--target-name=<TARGET_NAME>`
+
+Use this option in combination with the `--report` option. Set or override the target name for the project.
+
+### `--target-reference=<TARGET_REFERENCE>`
+
+Use this option in combination with the `--report` option. Specify a reference that differentiates this project, for example, a branch name or version. Projects with the same reference can be grouped based on that reference. Example of setting to the current Git branch:
+
+`snyk secrets test --report --target-reference="$(git branch --show-current)"`
+
+Example of setting to the latest Git tag:
+
+`snyk secrets test --report --target-reference="$(git describe --tags --abbrev=0)"`
+
+### `--project-environment=<ENVIRONMENT>[,<ENVIRONMENT>]...`
+
+Set the project environment project attribute to one or more comma-separated values. To clear the project environment, set `--project-environment=`. Allowed values: `frontend`, `backend`, `internal`, `external`, `mobile`, `saas`, `onprem`, `hosted`, `distributed`. For more information, see [Project attributes](https://app.gitbook.com/s/BJO0IZx7zB6bOkotxQP2/scan-with-snyk/snyk-projects/project-attributes)
+
+### `--project-lifecycle=<LIFECYCLE>[,<LIFECYCLE>]...`
+
+Set the project lifecycle project attribute to one or more comma-separated values. To clear the project lifecycle, set `--project-lifecycle=`. Allowed values: `production`, `development`, `sandbox`. For more information, see [Project attributes](https://app.gitbook.com/s/BJO0IZx7zB6bOkotxQP2/scan-with-snyk/snyk-projects/project-attributes)
+
+### `--project-business-criticality=<BUSINESS_CRITICALITY>[,<BUSINESS_CRITICALITY>]...`
+
+Set the project business criticality project attribute to one or more comma-separated values. To clear the project business criticality, set `--project-business-criticality=`. Allowed values: `critical`, `high`, `medium`, `low`. For more information, see [Project attributes](https://app.gitbook.com/s/BJO0IZx7zB6bOkotxQP2/scan-with-snyk/snyk-projects/project-attributes)
+
+### `--project-tags=<TAG>[,<TAG>]...`
+
+Set the project tags to one or more comma-separated key-value pairs with an `=` separator. Example: `snyk secrets test --project-tags=department=finance,team=alpha` To clear the project tags, set `--project-tags=`. For more information, including allowable characters, see [Project tags](https://app.gitbook.com/s/BJO0IZx7zB6bOkotxQP2/scan-with-snyk/snyk-projects/project-tags)
+
+### `--json`
+
+Print results to the console as a JSON data structure. Example: `snyk secrets test --json`
+
+### `--json-file-output=<OUTPUT_FILE_PATH>`
+
+Save test output as a JSON data structure directly to the specified file, regardless of whether you use the `--json` option. Use this option to display human-readable test output using `stdout` and, at the same time, save the JSON data structure output to a file. For Secrets, Snyk does not create a JSON file if no issues are found. For open source, Snyk creates a file whether or not issues are found. Example: `snyk secrets test --json-file-output=detected-secrets.json`
+
+### `--sarif`
+
+Return results in SARIF format. Example: `snyk secrets test --sarif`
+
+### `--sarif-file-output=<OUTPUT_FILE_PATH>`
+
+Save test output in SARIF format directly to the `<OUTPUT_FILE_PATH>` file, regardless of whether you use the `--sarif` option. Use this option to display human-readable test output using `stdout` and, at the same time, save the SARIF format output to a file. When running multiple scans, such as Secrets and Code scans, the SARIF output includes data only from the most recently completed scan. If you run multiple scans sequentially and specify the same `--sarif-file-output` file path, each subsequent scan overwrites the previous SARIF file. To keep results separate, save each scan to a different SARIF output file.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "snyk",
-  "version": "1.1306.3",
+  "version": "1.1306.4",
   "description": "snyk library and cli utility",
   "mcpName": "io.snyk/mcp",
   "files": [

package/src/generated/sha256sums.txt

@@ -1,9 +1,9 @@
-342fc5fcb4b6a43105329dde928491dee5968350b8eb52a5187f4b13639227d5  snyk-alpine-arm64
-a2bdff8e6efd27aa070c5dda5681d687e9ddbb45522efc9955c27c32f93b84be  snyk-alpine
-84dd03dc8cd7d4e80501d20d9737aff22b1ed5cd03a1fa62a28d679ac9d419d3  snyk-fix.tgz
-a31bb3b69ac88b1f1a7795e9a1800d834c3e843eede06a347d5cd13c955efe02  snyk-linux-arm64
-a76435dab2cecf567d2be13c5dd5dc5db1bc5959adf0f185e5f9419574ceb6fa  snyk-linux
-6affd215ef52f0eebaddd34e946c64bc8cfb06223387d8e6164a10501910fa92  snyk-macos-arm64
-b6fed621d28f16b712a8ea3c7121a3ecfab1ca806af41f08f86987c9c9f9b81f  snyk-macos
-c2e1042feeca60a4a83c3f7521cee244c37645cf7c0c32ff6200a9e7d9a3efd2  snyk-protect.tgz
-00d00dd69bdde4dda5bbd91add4c5a93c457d97c30673b2fe53ce633d3195df3  snyk-win.exe
+72aef488d0134231846dce8152973e14a4e9c2f07eb52a950c9aa0ba065da29e  snyk-alpine-arm64
+4177ff271cb6a434ea6f9613d8c6e7e0d7d66e4dd00e726d57371a2a50de9059  snyk-alpine
+d06a1e45addf9c852ec949b0cb782e065c9bd8561747d0fcaa70e638df12b503  snyk-fix.tgz
+d970aef55c25dc3cb5986853e69643aac7e20acf8c56ffbd304218f41470a7d2  snyk-linux-arm64
+78a83f57a16cb660879cb29f75fcb4a6c1ba07791dceb41e2b840fb89741c95c  snyk-linux
+c9f0ef8c4b555f3ac4eb6d3d874d2d06260a58d39e91dbcac4008cfb74c9ecbb  snyk-macos-arm64
+f902dbc0be77cd3778d2a7119cc7235e220cf2ef809171b17b95e295b2e23d35  snyk-macos
+dd5edfef8564d30c91d51df386737b03f5a1f31929d551a3a4e114818a123d4f  snyk-protect.tgz
+45e0a8f6f451b471e86e7d94ed9622e53b66f92b7e2bcc1a0680d3306f256296  snyk-win.exe

package/src/generated/version

@@ -1 +1 @@
-1.1306.3
+1.1306.4

package/wrapper_dist/generated/sha256sums.txt

@@ -1,9 +1,9 @@
-342fc5fcb4b6a43105329dde928491dee5968350b8eb52a5187f4b13639227d5  snyk-alpine-arm64
-a2bdff8e6efd27aa070c5dda5681d687e9ddbb45522efc9955c27c32f93b84be  snyk-alpine
-84dd03dc8cd7d4e80501d20d9737aff22b1ed5cd03a1fa62a28d679ac9d419d3  snyk-fix.tgz
-a31bb3b69ac88b1f1a7795e9a1800d834c3e843eede06a347d5cd13c955efe02  snyk-linux-arm64
-a76435dab2cecf567d2be13c5dd5dc5db1bc5959adf0f185e5f9419574ceb6fa  snyk-linux
-6affd215ef52f0eebaddd34e946c64bc8cfb06223387d8e6164a10501910fa92  snyk-macos-arm64
-b6fed621d28f16b712a8ea3c7121a3ecfab1ca806af41f08f86987c9c9f9b81f  snyk-macos
-c2e1042feeca60a4a83c3f7521cee244c37645cf7c0c32ff6200a9e7d9a3efd2  snyk-protect.tgz
-00d00dd69bdde4dda5bbd91add4c5a93c457d97c30673b2fe53ce633d3195df3  snyk-win.exe
+72aef488d0134231846dce8152973e14a4e9c2f07eb52a950c9aa0ba065da29e  snyk-alpine-arm64
+4177ff271cb6a434ea6f9613d8c6e7e0d7d66e4dd00e726d57371a2a50de9059  snyk-alpine
+d06a1e45addf9c852ec949b0cb782e065c9bd8561747d0fcaa70e638df12b503  snyk-fix.tgz
+d970aef55c25dc3cb5986853e69643aac7e20acf8c56ffbd304218f41470a7d2  snyk-linux-arm64
+78a83f57a16cb660879cb29f75fcb4a6c1ba07791dceb41e2b840fb89741c95c  snyk-linux
+c9f0ef8c4b555f3ac4eb6d3d874d2d06260a58d39e91dbcac4008cfb74c9ecbb  snyk-macos-arm64
+f902dbc0be77cd3778d2a7119cc7235e220cf2ef809171b17b95e295b2e23d35  snyk-macos
+dd5edfef8564d30c91d51df386737b03f5a1f31929d551a3a4e114818a123d4f  snyk-protect.tgz
+45e0a8f6f451b471e86e7d94ed9622e53b66f92b7e2bcc1a0680d3306f256296  snyk-win.exe

package/wrapper_dist/generated/version

@@ -1 +1 @@
-1.1306.3
+1.1306.4