Socket Basics SAST: use explicit secrets instead of secrets: inherit#32
Merged
Conversation
buffym
approved these changes
Jul 6, 2026
buffym
left a comment
buffym
left a comment
Member
There was a problem hiding this comment.
Verified identical to the batch: secrets: inherit → explicit SOCKET_SECURITY_API_KEY pass-through only.
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
2 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.
Summary
secrets: inheritwith an explicitSOCKET_SECURITY_API_KEYsecretsecrets: inheritpasses all secrets from the calling repo to shared-actions, violating least-privilege. Explicit secrets limit exposure to only what the workflow actually needs.Test plan