Skip to content

chore(ci): pin third-party actions to commit SHAs - #2739

Open
cs-raj wants to merge 1 commit into
developmentfrom
chore/pin-actions-sha
Open

cs-raj wants to merge 1 commit into
developmentfrom
chore/pin-actions-sha

Conversation

@cs-raj

@cs-raj cs-raj commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Problem

lint.yml, unit-test.yml and sca-scan.yml load third-party actions by a movable ref (pnpm/action-setup@v4, snyk/actions/node@master). If that ref is repointed, the next CI run executes the new code with this repo's token. Third-party actions should be pinned to a commit SHA.

Fix

  • pnpm/action-setup@v4 → @b906aff… # v4.3.0, the commit the floating v4 tag resolves to today.
  • snyk/actions/node@master → @9adf32b… # v1.0.0. node/action.yml is identical on master and v1.0.0.
  • Unchanged: GitHub-owned actions/* and github/codeql-action/*, our own contentstack/sca-policy@main, and the release workflows, which are being replaced separately.

Verified: the three edited files parse as valid YAML.

A tag or branch can be moved to point at different code; a commit SHA
cannot. Pin pnpm/action-setup and snyk/actions/node at the commit each
workflow already runs, so CI behaviour does not change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cs-raj
cs-raj requested a review from a team as a code owner October 22, 2026 13:33
@cs-raj cs-raj self-assigned this Oct 22, 2026
@snyk-io

snyk-io Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 131 25 ✅ Passed
🟡 Medium Severity 1 232 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

⚠️ Warning: The following vulnerabilities have exceeded their SLA thresholds (days since publication).

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 1 90 / 365 days ⚠️ Warning
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 131
  • Medium without fixes: 232
  • Low without fixes: 0

⚠️ BUILD PASSED WITH WARNINGS - SLA breaches detected for issues without available fixes

Consider reviewing these vulnerabilities when fixes become available.

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