chore: onboard stepsecurity and apply security best practice#34
Open
ali-kafel wants to merge 2 commits into
Open
chore: onboard stepsecurity and apply security best practice#34ali-kafel wants to merge 2 commits into
ali-kafel wants to merge 2 commits into
Conversation
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
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
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 pull request updates the GitHub Actions workflows for linting and testing to improve security and reliability. The main changes include hardening the runners, pinning all third-party actions to specific commit hashes for better supply chain security, and updating the permissions for jobs.
Security hardening and reliability improvements:
step-security/harden-runneraction to all jobs in.github/workflows/lint.ymland.github/workflows/test.ymlto restrict network egress and apply a global-allowed-endpoints policy. [1] [2]permissions: id-token: writefor all jobs to enable secure OIDC-based authentication for actions that require it. [1] [2]Dependency pinning for supply chain security:
Documentation and consistency:
.github/workflows/lint.ymlto also use pinned action SHAs for consistency, even though these steps are currently disabled.