Skip to content

ci: scorecard comment says what the job token reads #123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
askalf merged 1 commit into from
Sep 26, 2026
Merged

ci: scorecard comment says what the job token reads #123

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions .github/workflows/scorecard.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,11 +33,11 @@ jobs:
with:
results_file: results.sarif
results_format: sarif
# The default GITHUB_TOKEN can't read branch-protection settings, so the
# Branch-Protection check errors out (-1). A fine-grained PAT with
# `administration: read` + `metadata: read` (repo secret SCORECARD_TOKEN)
# lets it read them; falls back to the default token if the secret is
# unset (all other checks still run).
# Branch-Protection scores from what the job token can read: the public
# rules of a public repo (5-8 of 10 here, not the -1 an earlier comment
# claimed). A fine-grained PAT with `administration: read` + `metadata:
# read` in the SCORECARD_TOKEN secret would also read the admin-only
# settings; no repo sets one, so the fallback is the path every run takes.
repo_token: ${{ secrets.SCORECARD_TOKEN || github.token }}
publish_results: true

Expand Down
Loading