Skip to content

Potential fix for code scanning alert no. 74: Workflow does not contain permissions #884

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

Potential fix for code scanning alert no. 74: Workflow does not contain permissions #884

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
2 changes: 2 additions & 0 deletions .github/workflows/python-package.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ on:

jobs:
ci:
permissions:
contents: read
Comment on lines +16 to +17
Copy link

Copilot AI Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ci now has explicit least-privilege permissions, but cd still runs without a permissions block, so this workflow may still trip the same code-scanning rule (and cd will continue to get the default broad GITHUB_TOKEN scope). Consider setting explicit permissions for cd as well (likely contents: read), or defining a restrictive workflow-level default and overriding only where write access is needed (e.g., cb).

Copilot uses AI. Check for mistakes.
env:
# Fake a TRAVIS env so that the pre-existing test cases would behave like before
TRAVIS: true
Expand Down
Loading