Skip to content

fix(scorecard): scope budget-cadence permissions job-level (TokenPermissionsID) #679

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
AceHack merged 1 commit into from
Apr 28, 2026
Merged

fix(scorecard): scope budget-cadence permissions job-level (TokenPermissionsID) #679

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
30 changes: 18 additions & 12 deletions .github/workflows/budget-snapshot-cadence.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,18 +75,10 @@ on:
default: ""

permissions:
# Need contents:write to push the snapshot branch; pull-requests:write
# to open the snapshot PR; actions:read so snapshot-burn.sh can call
# the Actions REST endpoints (/repos/.../actions/runs and
# /actions/runs/{id}/timing) to populate burn metrics. Without
# actions:read, those API calls 403 silently and snapshot-burn.sh
# falls back to empty/zeroed timing data while still writing a
# snapshot — producing misleading evidence rather than a hard
# failure. With explicit workflow permissions, omitted scopes are
# `none`, so actions:read MUST be listed explicitly here.
contents: write
pull-requests: write
actions: read
# Top-level: read-only by default (per Scorecard TokenPermissions
# best-practice — minimize blast radius if any step is compromised).
# The snapshot job below scopes write permissions narrowly.
contents: read

concurrency:
# Only one cadence run at a time. Retriggers queue (rather than
Expand All @@ -101,6 +93,20 @@ jobs:
runs-on: ubuntu-24.04
timeout-minutes: 5

permissions:
# Need contents:write to push the snapshot branch; pull-requests:write
# to open the snapshot PR; actions:read so snapshot-burn.sh can call
# the Actions REST endpoints (/repos/.../actions/runs and
# /actions/runs/{id}/timing) to populate burn metrics. Without
# actions:read, those API calls 403 silently and snapshot-burn.sh
# falls back to empty/zeroed timing data while still writing a
# snapshot — producing misleading evidence rather than a hard
# failure. With explicit job permissions, omitted scopes are
# `none`, so actions:read MUST be listed explicitly here.
contents: write
pull-requests: write
actions: read

steps:
- name: Checkout
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
Expand Down
Loading