Skip to content

Fix/tokens-permissions#61

Open
andrefelizardo wants to merge 4 commits intomainfrom
fix/tokens-permissions
Open

Fix/tokens-permissions#61
andrefelizardo wants to merge 4 commits intomainfrom
fix/tokens-permissions

Conversation

@andrefelizardo
Copy link
Collaborator

Eliminate Token-Permissions warnings from the OpenSSF Scorecard check by following the documented guidance for least-privilege GitHub Actions tokens

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: af2665ccb5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines 14 to 16
permissions:
security-events: write
id-token: write

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore read scopes in scorecard job permissions

This job-level permissions block now grants only security-events and id-token; in GitHub Actions, once a job declares specific permissions, unspecified scopes are treated as none, so contents/actions read access from the workflow default is not retained. That can break actions/checkout and SARIF upload behavior when this workflow runs in private mirrors/forks (or if visibility changes), because those steps rely on repository/actions read access.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants