Repository navigation
Scorecard: least-privilege workflow tokens and other fixes - #330
Merged
Merged
Conversation
Shared admin callers get an empty top-level permissions block; each job keeps its own grants (synced from rhizomatics/hq admin/templates). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
OpenSSF Scorecard findings, fixed:
admin-*.yml): an empty top-levelpermissions: {}, so nothing gets the repo's default write token; each job keeps the grants it already had. Synced fromrhizomatics/hqadmin/templates/workflows/.release.yml: its write grants move from the top level to thepublishjob (Scorecard scored Token-Permissions 0 for the top-level write).No change to what any workflow can do: every job already declared its permissions.
🤖 Generated with Claude Code