crickets-and-comb/shared

Pin third-party actions to commit SHAs

Open

#39 opened on Mar 22, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Makefile (0 forks)auto 404
bughelp wanted

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

Sounds like best practice is not to simply pin to a version to get the latest patch updates, but to pin to a specific commit SHA.

For all calls to third-party actions, pin to a specific SHA, copied directly from the action source.

Kaleb: Set up a periodic review of SHAs or ensure that security alerts will issue for specific SHAs.

Contributor guide

Research direction
Find all workflow files in the repository that use third party GitHub Actions. For each action, replace the version tag (e.g., `v1`) with the exact commit SHA from the action's repository. Ensure the SHA is pinned without any semver range. Optionally, set up a periodic review schedule to update SHAs.
Tech stack
github actions
Domain
ci cdsecurity
Issue type
Security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitYAML
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90