You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -620,6 +621,7 @@ The Cycode CLI application offers several types of scans so that you can choose
620
621
|`--monitor`| When specified, the scan results will be recorded in Cycode. |
621
622
|`--cycode-report`| Display a link to the scan report in the Cycode platform in the console output. |
622
623
|`--no-restore`| When specified, Cycode will not run the restore command. This will scan direct dependencies ONLY!|
624
+
|`--stop-on-error`| Abort the scan if any file collection or dependency restore failure occurs, instead of skipping the failed file and continuing. |
623
625
|`--gradle-all-sub-projects`| Run gradle restore commandfor all sub projects. This should be run from |
624
626
|`--maven-settings-file`| For Maven only, allows using a custom [settings.xml](https://maven.apache.org/settings.html) file when scanning for dependencies |
625
627
|`--help`| Show options for given command. |
@@ -726,6 +728,18 @@ If a lockfile already exists alongside the manifest, Cycode reads it directly wi
By default, Cycode continues scanning even if a file cannot be read (e.g. due to a permission error) or a dependency lockfile cannot be generated during an SCA scan. The failed item is skipped with a warning and the scan proceeds with the remaining files.
734
+
735
+
Use `--stop-on-error` to change this behaviour: the scan aborts immediately on the first such failure and reports the error.
This is useful in CI pipelines where a silent failure would produce an incomplete scan result. When `--stop-on-error` is triggered you can either fix the underlying issue or, for SCA restore failures specifically, add `--no-restore` to skip lockfile generation and scan direct dependencies only.
742
+
729
743
### Repository Scan
730
744
731
745
A repository scan examines an entire local repository for any exposed secrets or insecure misconfigurations. This more holistic scan type looks at everything: the current state of your repository and its commit history. It will look not only for secrets that are currently exposed within the repository but previously deleted secrets as well.
0 commit comments