chore: apply security best practices and onboard stepsecurity#7
Open
ali-kafel wants to merge 2 commits into
Open
chore: apply security best practices and onboard stepsecurity#7ali-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
1 participant
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 strengthens the security and reliability of the GitHub Actions workflows for Recibo by hardening the runner environment, updating permissions, and pinning action versions to specific commit SHAs. These changes help prevent unauthorized access and ensure consistent, reproducible builds.
Security enhancements:
step-security/harden-runneraction to both.github/workflows/recibo_test.yamland.github/workflows/recibo_python_test.yamlto block unauthorized egress traffic and apply a global allowed endpoints policy. [1] [2]permissions: id-token: writeto enable secure use of OpenID Connect tokens in both workflows. [1] [2]Reliability improvements:
actions/checkoutandfoundry-rs/foundry-toolchainactions to use specific commit SHAs instead of floating versions, reducing the risk of unexpected changes from upstream updates. [1] [2]