ci: add GitHub token permissions for workflow#16033
Merged
sokra merged 1 commit intowebpack:mainfrom Jul 25, 2022
Merged
Conversation
Signed-off-by: Varun Sharma <varunsh@stepsecurity.io>
|
|
Contributor
|
For maintainers only:
|
alexander-akait
approved these changes
Jul 10, 2022
sokra
approved these changes
Jul 25, 2022
Member
|
Thanks |
32 tasks
87 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 PR adds minimum token permissions for the GITHUB_TOKEN using https://github.com/step-security/secure-workflows.
GitHub recommends defining minimum GITHUB_TOKEN permissions for securing GitHub Actions workflows
This project is part of the top 100 critical projects as per OpenSSF (https://github.com/ossf/wg-securing-critical-projects), so fixing the token permissions to improve security.
Signed-off-by: Varun Sharma varunsh@stepsecurity.io
What kind of change does this PR introduce?
Build related change
Did you add tests for your changes?
New tests not needed for the change
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
Not applicable