Skip to content

Harden CI supply chain: pin third-party actions to SHAs #24

Description

@santidev21

SonarCloud flags the CI supply chain (rules S7637 / S6505 / S8543). Triaged as accepted for now and deferred so the security-triage change stays focused.

Scope

  • S7637 — third-party uses: entries are pinned to mutable tags instead of commit SHAs (gitleaks, docker/*, aquasecurity/trivy-action, appleboy/ssh-action).
  • S6505 / S8543 — npm ci / npx steps run lifecycle scripts and npx is not explicitly restricted to the lockfile-pinned local install.

Proposal

  • Pin each third-party action to its commit SHA with a # vX.Y.Z comment so Dependabot keeps updating it.
  • Use npx --no-install (or the local node_modules/.bin binary) instead of bare npx where no install is intended.
  • Keep lifecycle scripts enabled where the build requires them (Angular/esbuild postinstall); document the exceptions.

Related: T2 security triage.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions