Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should have no effective changes, but I think it will improve the OpenSSF Scorecard result.
Workflow level permissions are called "top level" permissions and are calculated around here: https://github.com/ossf/scorecard/blob/8779de9cd23ffe15b6fd398a2f125a3452f08170/checks/raw/permissions.go#L267
Write permissions at the top level seem to be discouraaged.
Individual workflows are inspected for actions that fingerprint - I think because our workflow includes
actions/setup-go
andgoreleaser/goreleaser-action
, it will be considered to require thecontents: write
andpackages: write
permissions. This is calculated around here - https://github.com/ossf/scorecard/blob/8779de9cd23ffe15b6fd398a2f125a3452f08170/checks/raw/permissions.go#L336-L351TLDR: should not break anything, might boost scorecard by 0.1 📈
Related