aboutsummaryrefslogtreecommitdiff
path: root/version
diff options
context:
space:
mode:
authornaveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>2022-03-18 23:56:02 +0000
committernaveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>2022-03-28 19:00:16 +0000
commit1821eb3837a81bf666ed87e5ccb3da4e190a9aba (patch)
treebd9f7fea260a1c602d0c9a77406eac4f3a67b0c2 /version
parentc2eae35c606382418c6e2ce57c4ab874f1975f21 (diff)
downloadpodman-1821eb3837a81bf666ed87e5ccb3da4e190a9aba.tar.gz
podman-1821eb3837a81bf666ed87e5ccb3da4e190a9aba.tar.bz2
podman-1821eb3837a81bf666ed87e5ccb3da4e190a9aba.zip
Pin actions to a full length commit SHA
- Pinned actions by SHA https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions >Pin actions to a full length commit SHA >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. https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions Also dependabot supports upgrades based on SHA. Signed-off-by: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>
Diffstat (limited to 'version')
0 files changed, 0 insertions, 0 deletions