SHA-pin the GitHub Actions that hold secrets or publish (claude-code-action, release job)

Look at the workflow files listed in the issue: sdk-watch.yml and main.yml. Identify the jobs that use secrets (ANTHROPIC_API_KEY, npm OIDC, packages: write). For each action in those jobs, replace the mutable tag (like @v7) with the provided commit SHA, adding a comment. Verify the changes by running the workflows in a test environment or checking the syntax. The monthly dependency-refresh sweep will report if these SHAs become stale.

Severity: Low to Medium. CWE: CWE-829. Related: #1882 (earlier SHA-pinning of claude.yml, closed) and #2235 (decision to leave actions on moving major tags and report staleness via the monthly sweep).

What

I understand from #2235 that the actions are deliberately on moving major tags (@v4/@v7) and that staleness is reported by the
monthly sweep. This issue does not ask to revisit that everywhere. It asks for a narrower rule: pin by commit SHA the actions that run in a
job with a secret or a publish credential, where a moved tag replaces the code holding the credential.

For scale: Semgrep github-actions-mutable-action-tag reports 24 uses: lines; OpenSSF Scorecard (CLI, 2026-09-24) gives
Pinned-Dependencies 1/10 (overall 7.7; Token-Permissions 10, Dangerous-Workflow 10, Vulnerabilities 10, Dependency-Update-Tool 10, SAST 0, Branch-Protection 5).

Commit SHAs resolved on 2026-09-24 (re-verify before use; tags move)

Suggested change

• Pin those refs to SHAs with a trailing # vN comment, and let the monthly dependency-refresh sweep report stale SHAs the way #2235 option A describes.
• Optionally add an OpenSSF Scorecard workflow, and a small CI check that any uses: in a job holding a secret is a 40-hex ref.

Reviewed and not a finding

permissions: are least-privilege in every workflow, there is no pull_request_target, and ${{ }} expressions reach run: only through
env:. sdk-watch.yml correctly splits the model job (read-only, Read/Grep/Glob only) from the write job.

Reviewed at 1e31c78 (v2.8.0). No fix code is offered, per CONTRIBUTING.md.

Prompt used (per CONTRIBUTING.md)

"Audit this repository's CI workflows and one crypto module against the OpenSSF/CRA-friendly checklist. Run Semgrep,
osv-scanner, gitleaks and trufflehog; read every cited line before accepting a finding; reproduce any crypto claim on the
lowest supported Node version; drop findings that are test fixtures or already mitigated."