actions-marketplace-validations/Cynalytica Container image scan
Scan container images for vulnerabilities and issues from scan
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Mar 9, 2022
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: actions-marketplace-validations/cynalytica_container-scan@dd7eed0f4656671cae2d9b5f3cf8d3b5535c4f97 # no releases — HEAD as of 2026-07-13tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| image-names | Docker images to scan, comma or space seperated image list to scan | yes | — |
| severity-threshold | (Optional) Minimum severity threshold set to control flagging of the vulnerabilities found during the scan. The available levels are: (UNKNOWN, LOW, MEDIUM, HIGH, CRITICAL); if you set the severity-threshold to be `MEDIUM` every CVE found of a level higher than or equal to `MEDIUM` would be displayed | no | MEDIUM |
| wont-fix-label | Label to identify the closed issues that should not be re-opened from this action. | yes | wontfix |
| no-fix-label | Label to use to tag CVE's that have no known fix at the moment | yes | no-fix |
| is-fixed-label | User applied label to prevent issues from being reopened. | yes | fixed |
| max-create-retry | Maximum number of times to try and create an issue. otherwise just call it a day. | no | 2 |
| username | Username to authenticate to the Docker registry | no | — |
| password | Password to authenticate to the Docker registry | no | — |
| token | Github token | yes | ${{ github.token }} |
| run-issue-create | Create issues on the repo instead of using SARIF reports. | no | false |
Outputs
| name | description |
|---|---|
| sarif-report-path | File path where the scan results are stored |
| audit-reports-path | File path where the scan results are stored |