Tighten GitHub Actions token permissions for Scorecard hardening#626
Draft
Tighten GitHub Actions token permissions for Scorecard hardening#626
Conversation
Co-authored-by: oocx <584396+oocx@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Improve OpenSSF score with meaningful changes
Tighten GitHub Actions token permissions for Scorecard hardening
Mar 18, 2026
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
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.
Summary
This reduces default
GITHUB_TOKENscope in two workflows to improve the repo’s OpenSSF posture without changing behavior. The change removes an unnecessary broad read grant in the Scorecard workflow and narrows PR validation from PR-write access to the Issues API scope it actually uses.Problem
Change
pr-validation.ymlpull-requests: writewithissues: writegithub.rest.issues.*scorecard.ymlpermissions: read-allwithpermissions: {}Result
Checklist
Merge method: Use Rebase and merge to maintain a linear history. The repository enforces rebase-only merges by default.
Create & merge guidance: Use
scripts/pr-github.sh createto create PRs, andscripts/pr-github.sh create-and-mergeto perform the merge (this script is the authoritative, repo-preferred tool for PR creation and merges). If you need to inspect/check the PR, use GitHub chat tools (github/*) as needed.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
api.securityscorecards.dev/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)scorecard.dev/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.