ci(scorecard): wire the OpenSSF Scorecard action#15
Merged
Conversation
…ublished results)
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.
Wires the OpenSSF Scorecard action into this repo (same workflow the rest of the fleet runs: redstamp, truecopy, strongroom, fieldpass, hybrid, cordon).
Weekly + on-push analysis of supply-chain posture (pinned deps, token permissions, CI tests, …).
publish_results: truefeeds the public scorecard.dev API; the SARIF lands in code scanning. Uses the defaultGITHUB_TOKENunless aSCORECARD_TOKENfine-grained PAT (administration:read + metadata:read) is added as a repo secret — only the Branch-Protection check needs that; everything else runs without it.