2 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
NaveenandAleksandar Vidakovic	69a900492c	chore: renovate bot setting to pin actions to a full length commit SHA ... - https://docs.renovatebot.com/modules/manager/github-actions/#additional-information - Pinned actions by SHA https://github.com/ossf/scorecard/blob/main/docs/checks.md#pinned-dependencies >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 - https://github.com/renovatebot/.github/blob/b0c3aa85ef2bb242580f20b02b380ca532b4ce17/default.json#L13	2022-05-20 19:31:21 +02:00
naveensrinivasanandAleksandar Vidakovic	e088e4d70d	chore: Set permissions for GitHub actions ... Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>	2022-04-21 13:46:58 +02:00