Skip to content

fix(ci): pin action SHAs in security-scan.yml to prevent supply-chain attacks#32

Merged
tehw0lf merged 1 commit into
mainfrom
fix/pin-action-shas
Jul 2, 2026
Merged

fix(ci): pin action SHAs in security-scan.yml to prevent supply-chain attacks#32
tehw0lf merged 1 commit into
mainfrom
fix/pin-action-shas

Conversation

@tehw0lf

@tehw0lf tehw0lf commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • Pins dawidd6/action-download-artifact@v6 and actions/upload-artifact@v4 to full commit SHAs in security-scan.yml, resolving the Semgrep github-actions-mutable-action-tag finding (mutable tags can be silently repointed by the action owner, enabling supply-chain attacks).

Test plan

  • CI passes (lint/test/build)
  • Semgrep security scan no longer flags github-actions-mutable-action-tag for these two steps

… attacks

Pins dawidd6/action-download-artifact and actions/upload-artifact
to full commit SHAs instead of mutable version tags, resolving
Semgrep findings (github-actions-mutable-action-tag).
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9f2bbccd-f94c-4ecb-8681-5f9243c68626

📥 Commits

Reviewing files that changed from the base of the PR and between 1e0c9ed and 1a9006e.

📒 Files selected for processing (1)
  • .github/workflows/security-scan.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/pin-action-shas

Comment @coderabbitai help to get the list of available commands.

@tehw0lf tehw0lf merged commit e7d10ad into main Jul 2, 2026
20 checks passed
@tehw0lf tehw0lf deleted the fix/pin-action-shas branch July 2, 2026 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant