security: scope CLA workflow token permissions to job level#16
Merged
Merged
Conversation
Top-level permissions set to none; the four scopes CLA Assistant Lite requires (actions, contents, pull-requests, statuses) are now granted only to the cla job. Same effective privilege today (single job), but future jobs no longer inherit write access and the workflow follows the least-privilege pattern recommended for pull_request_target. Same change already merged and verified live in gen-fraud-graph#24. No behavior change.
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.
What
Moves the four token scopes CLA Assistant Lite needs (
actions,contents,pull-requests,statuses) from workflow level to theclajob, and sets the top-level default to none (permissions: {}).Why
Least privilege for a
pull_request_targetworkflow: same effective permissions today (single job), but nothing is inherited by future jobs. Addresses the OpenSSF Scorecard Token-Permissions findings for this workflow.Verification
Identical change merged in SantanderAI/gen-fraud-graph#24 and verified live: a
recheckon an open external PR re-ran the CLA bot frommainwith job-level permissions, concludingsuccess.