Skip to content

KICS

KICS #158

Triggered via schedule March 17, 2024 00:13
Status Success
Total duration 51s
Artifacts

kics.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Analyze
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: github/codeql-action/upload-sarif@689fdc5193eeb735ecb2e52e819e3382876f93f4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
[MEDIUM] Unpinned Actions Full Length Commit SHA: .github/workflows/build.yml#L96
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#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.
[MEDIUM] Unpinned Actions Full Length Commit SHA: .github/workflows/helm-chart-lint.yml#L71
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.