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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚨 suggestion (security): Consider scoping
id-token: writeto the specific job that requires it rather than at the workflow level.This makes OIDC tokens available to every job. To follow least-privilege, only enable
id-token: writein thepermissionsblock of the specific jobs that actually need it, keeping the workflow-wide permissions minimal.Suggested implementation:
To fully implement least-privilege, add a
permissionsblock to the specific job(s) that actually require OIDC, for example:Adjust the job name and permissions according to the actual job in this workflow that uses OIDC (e.g. for cloud auth/deploy). Other jobs should omit
id-token: write.