Using `@v1` should not be recommended (absent immutable versions)
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/actions/toolkit/blob/1b1e81526b802d1d641911393281c2fb45ed5f11/docs/action-versioning.md?plain=1#L9
This contradicts:
https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-third-party-actions
You can help mitigate this risk by following these good practices:
Pin actions to a full length commit SHA
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked section of docs/action-versioning.md and compare its guidance with GitHub’s security-hardening guide linked in the issue. Done means the recommendation about using @v1 no longer contradicts the guidance to pin actions to a full-length commit SHA.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100