Skip to content

[Aikido] AI Fix for Overly Broad Permissions in GitHub Actions Workflows is risky #17

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
yosriady merged 1 commit into from
Jul 7, 2026
Merged

[Aikido] AI Fix for Overly Broad Permissions in GitHub Actions Workflows is risky #17

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
7 changes: 4 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,15 +5,16 @@ on:
tags:
- 'v*'

permissions:
id-token: write # Required for OIDC trusted publishing
contents: write # Required for creating GitHub releases
permissions: {}

jobs:
publish:
# npm provenance publishing only supports GitHub-hosted Actions runners.
# Keep this job on ubuntu-latest unless npm adds self-hosted provenance support.
runs-on: ubuntu-latest
permissions:
contents: read
id-token: write # Required for OIDC trusted publishing
# Workflow-context values are bound to env here and referenced as
# shell variables ($TAG/$REPO/$COMMIT_SHA) in run: blocks instead of
# `${{ }}` interpolation, so an attacker-controlled tag name cannot be
Expand Down