ci: declare workflow-level contents: read on the 9 python-N.yml build workflows#412
Open
arpitjain099 wants to merge 1 commit into
Open
Conversation
… workflows Pins the default GITHUB_TOKEN to contents: read on the per-Python- version build workflows. Each one runs sphinx-build / msgfmt against the translated rst files and uploads the rendered HTML as a workflow artifact - no GitHub API mutation. - python-37.yml, python-38.yml, python-39.yml, python-310.yml, python-311.yml, python-312.yml, python-313.yml, python-314.yml, python-315.yml update-tx-config.yml is intentionally left implicit; it commits and pushes via GITHUB_TOKEN, so the scope is best declared by the maintainer who owns the translation-sync flow. Motivation: CVE-2025-30066 (March 2025 tj-actions/changed-files compromise) exfiltrated GITHUB_TOKEN from workflow logs. Per-workflow caps bound runtime authority irrespective of repo or org default, give drift protection if the default ever widens, and are credited per-file by the OpenSSF Scorecard Token-Permissions check. YAML validated locally with yaml.safe_load. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
arpitjain099
force-pushed
the
chore/declare-workflow-perms-readonly
branch
from
4ad78b8 to
43e70df
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pins the default
GITHUB_TOKENtocontents: readon the per-Python-version build workflows. Each one runs sphinx-build / msgfmt against the translated rst files and uploads the rendered HTML as a workflow artifact, with no GitHub API mutation:python-37.yml,python-38.yml,python-39.yml,python-310.yml,python-311.yml,python-312.yml,python-313.yml,python-314.yml,python-315.ymlupdate-tx-config.ymlis intentionally left implicit; it commits and pushes viaGITHUB_TOKEN, so the scope is best declared by a maintainer who owns the translation-sync flow.Why
CVE-2025-30066 (March 2025
tj-actions/changed-filessupply-chain compromise) exfiltratedGITHUB_TOKENfrom workflow logs and the leaked token retained whatever scope was issued at the workflow level. Pinning per workflow caps that runtime authority irrespective of the repo or org default, gives drift protection if the default ever widens, and is credited per-file by the OpenSSF ScorecardToken-Permissionscheck.YAML validated locally with
yaml.safe_loadon each touched file.