Idea: pin github actions to a known-good version

Open Beginner friendly
#808 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Review ci.yml and GitHub's third-party action pinning guidance; identify every mutable action reference and verify known-good commit SHAs. Update those references in ci.yml and confirm that all actions are pinned to full commit hashes.

Written by the indexing model from the issue text.

Description

References in ci.yml like, e.g., actions/setup-java@v4 are apparently to mutable tags. We could instead pin them to "known-good" versions, like actions/setup-java@3a4f6e1af504cf6a31855fa899c6aa5355ba6c12. As recommended by https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-third-party-actions.

Dominant language
Scala
Stars
185
Forks
62
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from typelevel/sbt-typelevel

All issues in typelevel/sbt-typelevel

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.