Repository navigation
chore(CLS-493): migrate to StepSecurity maintained action forks - #59
Open
stepsecurity-app[bot] wants to merge 1 commit into
Open
stepsecurity-app[bot] wants to merge 1 commit into
stepsecurity-app[bot] wants to merge 1 commit into
Conversation
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
Oplane Security ReviewOplane identified security requirements relevant to this PR and checked the implementation against them. All requirements are satisfied. Review the generated threat model.
Change comment settings · Set up Oplane in your agent · Workflow guidance |
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.
Motivation
Replace community-maintained GitHub Actions with StepSecurity-maintained forks as part of the CI/CD supply chain security hardening initiative (CLS-493).
StepSecurity-maintained forks include security monitoring, egress controls, and are covered by Miro's enterprise subscription.
Note: Only community/unmaintained actions are replaced. Official vendor actions (docker/, hashicorp/, google-github-actions/, anthropics/, etc.) are excluded and not modified by this PR.
Proposed changes
Pinned Dependencies
Pinning GitHub Actions to specific versions or commit SHAs ensures that your workflows remain consistent and secure.
Unpinned actions can lead to unexpected changes or vulnerabilities caused by upstream updates.
StepSecurity Maintained Actions
Risky GitHub Actions can expose your project to potential security risks. Risky actions have been replaced with StepSecurity maintained actions, that are secure drop-in replacements.
Testing
Related