Skip to content

docs: add required token permissions to CodeQL/Scorecard caller templates - #9

Merged
00o-sh merged 1 commit into
mainfrom
claude/new-session-zrgq01
Aug 12, 2026
Merged

docs: add required token permissions to CodeQL/Scorecard caller templates#9
00o-sh merged 1 commit into
mainfrom
claude/new-session-zrgq01

Conversation

@00o-sh

@00o-sh 00o-sh commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

What & why

The copy-paste caller templates for codeql.yml and scorecard.yml omitted the
permissions block. Because a reusable workflow's permissions are capped by the caller,
that omission makes Scorecard fail at startup on every fork — reusable-scorecard needs
id-token: write (for publish_results), which is never in the default GITHUB_TOKEN.

Updated both caller templates to show the required per-job scopes:

  • codeql.ymlactions: read, contents: read, security-events: write
  • scorecard.ymlsecurity-events: write, id-token: write, contents: read

New forks now wire these up from the start, and the scanners are independent of the org's
default token permissions. (The live forks are getting the same fix in their own PRs.)


Generated by Claude Code

…ates

Reusable-workflow permissions are capped by the caller, and the security
scanners need scopes not present in the default GITHUB_TOKEN (Scorecard needs
id-token: write, which is never granted by default). Show the required
per-job permissions in the caller templates so new forks wire them up and
Scorecard does not fail at startup.
@00o-sh
00o-sh merged commit bf28991 into main Aug 12, 2026
1 check passed
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.

2 participants