This repository was archived by the owner on Sep 15, 2026. It is now read-only.
Repository navigation
[StepSecurity] Apply security best practices - #212
Closed
stepsecurity-app[bot] wants to merge 1 commit into
Closed
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>
yonidavidson
approved these changes
Sep 10, 2026
yonidavidson
left a comment
yonidavidson
left a comment
There was a problem hiding this comment.
Approving StepSecurity Harden-Runner audit-mode remediation PR (workflow-only change, no failing checks).
|
Closing so StepSecurity can regenerate without the google-github-actions/auth swap (Tabnine tenant exception applied). |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
This pull request has been generated by StepSecurity as part of your enterprise subscription to ensure compliance with recommended security best practices. Please review and merge the pull request to apply these security enhancements.
Security Fixes
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.
Keeping your actions up to date with Dependabot
With Dependabot version updates, when Dependabot identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. This is recommended by GitHub as well as The Open Source Security Foundation (OpenSSF).
Runner Label Replacement
Runner labels define where GitHub Actions workflows execute. Replacing runner labels allows you to migrate workflows from one runner environment to another, such as moving from GitHub-hosted runners to self-hosted runners or vice versa.
This control automatically updates runner labels across your workflows based on the configured label mapping, ensuring consistent runner usage across your repository.
Feedback
For bug reports, feature requests, and general feedback; please create an issue in step-security/secure-repo or contact us via our website.