Skip to content

Potential fix for code scanning alert no. 79: Workflow does not contain permissions #149

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
devld merged 2 commits into from
Apr 12, 2026
Merged

Potential fix for code scanning alert no. 79: Workflow does not contain permissions #149

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2fa74ae
Potential fix for code scanning alert no. 79: Workflow does not conta…
devld Apr 12, 2026
f4f1e32
Potential fix for code scanning alert no. 80: Workflow does not conta…
devld Apr 12, 2026
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
3 changes: 3 additions & 0 deletions .github/workflows/docker-image.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ on:
description: "Already created tag"
required: true

permissions:
contents: read

jobs:
buildx:
runs-on: ubuntu-latest
Expand Down
4 changes: 4 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,10 @@ on:
tags:
- v*

permissions:
contents: write
actions: write
Copy link
Copy Markdown

@cursor cursor Bot Apr 12, 2026

Choose a reason for hiding this comment

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

Unnecessary actions: write permission violates least privilege

Low Severity

The actions: write permission is granted but not needed by any step in this workflow. Standard actions/cache@v4 save/restore operations use the ACTIONS_RUNTIME_TOKEN internally, not the GITHUB_TOKEN, so they don't require actions: write. That permission is only needed for cache deletion via gh cache delete or the REST API, which this workflow doesn't do. Since the PR's stated goal is to apply least-privilege permissions, granting actions: write unnecessarily widens the attack surface by allowing the token to cancel workflow runs, delete artifacts, and manage workflow dispatch events.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit f4f1e32. Configure here.


jobs:
build:
name: Build
Expand Down
Loading