Skip to content

chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 2.42.0 to 2.43.0 #409

chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 2.42.0 to 2.43.0

chore(deps): bump com.diffplug.spotless:spotless-maven-plugin from 2.42.0 to 2.43.0 #409

Triggered via pull request January 23, 2024 22:32
Status Success
Total duration 53s
Artifacts

kics.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
[MEDIUM] Unpinned Actions Full Length Commit SHA: .github/workflows/build.yml#L95
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#L65
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#L48
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.