Skip to content

Update Trivy GitHub Action to v0.35.0 #2031

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
mattisonchao merged 1 commit into from
Mar 23, 2026
Merged

Update Trivy GitHub Action to v0.35.0 #2031

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: 1 addition & 1 deletion .github/workflows/ci-trivy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ jobs:
run: docker build -f docker/amd64-linux.Dockerfile -t pulsarctl .

- name: Run Trivy vulnerability scanner
uses: aquasecurity/trivy-action@master
uses: aquasecurity/trivy-action@v0.35.0
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 23, 2026

Choose a reason for hiding this comment

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

P1 Badge Pin Trivy action to a full commit SHA

Replacing @master with @v0.35.0 still leaves this workflow consuming a mutable third-party ref. GitHub’s secure-use docs say a full commit SHA is “the only way to use an action as an immutable release” and explicitly note that tags can be moved or deleted, so if Aqua retargets v0.35.0 (or their repo is compromised again) this PR job will execute different code than the release you reviewed. To actually remove the supply-chain exposure this change is addressing, pin the vetted v0.35.0 commit SHA instead.

Useful? React with 👍 / 👎.

with:
image-ref: 'pulsarctl:latest'
format: 'table'
Expand Down
Loading