Skip to content

chore(deps): bump docker/build-push-action from 5.0.0 to 6.3.0 #199

chore(deps): bump docker/build-push-action from 5.0.0 to 6.3.0

chore(deps): bump docker/build-push-action from 5.0.0 to 6.3.0 #199

Triggered via pull request July 9, 2024 11:54
Status Success
Total duration 48s
Artifacts

kics.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Analyze
The following actions uses Node.js version which is deprecated and will be forced to run on node20: github/codeql-action/upload-sarif@689fdc5193eeb735ecb2e52e819e3382876f93f4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
[MEDIUM] Unpinned Actions Full Length Commit SHA: .github/workflows/veracode.yml#L70
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.
[MEDIUM] Unpinned Actions Full Length Commit SHA: .github/workflows/veracode.yml#L50
Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload. When selecting a SHA, you should verify it is from the action's repository and not a repository fork.