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
By default, if any vulnerability at `medium` or higher is seen, the build fails. To have the build step fail in cases where there are vulnerabilities with a severity level different than the default, set the `severity-cutoff` field to one of `low`, `high`, or `critical`:
@@ -99,12 +116,13 @@ Optionally, change the `fail-build` field to `false` to avoid failing the build
99
116
100
117
### Action Inputs
101
118
102
-
The only required key is `image` or `path`; all the other keys are optional. These are all the available keys to configure this action, along with its defaults:
119
+
The inputs `image`, `path`, and `sbom` are mutually exclusive to specify the source to scan; all the other keys are optional. These are all the available keys to configure this action, along with the defaults:
| `image` | The image to scan, this is mutually exclusive to `path` | N/A |
107
-
| `path` | The file path to scan, this is mutually exclusive to `image` | N/A |
123
+
| `image` | The image to scan | N/A |
124
+
| `path` | The file path to scan | N/A |
125
+
| `sbom` | The SBOM to scan | N/A |
108
126
| `debug` | Verbose logging output | `false` |
109
127
| `fail-build` | Fail the build if a vulnerability is found with a higher severity. That severity defaults to `"medium"` and can be set with `severity-cutoff`. | `true` |
110
128
| `acs-report-enable` | Generate a SARIF report and set the `sarif` output parameter after successful action execution. This report is compatible with GitHub Automated Code Scanning (ACS), as the artifact to upload for display as a Code Scanning Alert report. | `true` |
0 commit comments