Uh oh!
There was an error while loading. Please reload this page.
SEC1-7010: Pin GitHub Actions - #1
Merged
rnesargi-cedar merged 1 commit intoFeb 9, 2026
Merged
Conversation
rnesargi-cedarforce-pushed
the
rnesargi/SEC1-7010-pin-python-semantic-release-github-actions
branch
from
February 9, 2026 22:13
a063ab6 to
c0fc8cfComparernesargi-cedarforce-pushed
the
rnesargi/SEC1-7010-pin-python-semantic-release-github-actions
branch
from
February 9, 2026 22:16
c0fc8cf to
1173863CompareUh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Rationale
Pin GitHub Actions in security workflows to full commit SHAs so CI uses fixed, auditable versions and avoids supply-chain risk from moving tags/branches.
Solution
Replaced tag/branch refs with full 40-character SHAs.
Test Plan
List the steps to view your change locally, if possible.
N/A
If you did not add automated tests, explain why.
N/A
How will you confirm this works after it has been deployed?
N/A
Security Impact
Does this involve authentication, permissions, secrets or encryption?
No
Will this change allow humans to enter data into Cedar?
No
Will this change collect a new type of data? For example, introducing the collection of driver's licenses when we didn't collect them before, etc.
No
Does this PR add new vendors or add/update (python, JS, etc.) libraries?
No
Are there any security questions?
No
Additional Reviewers
N/A