Securely pin node version
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Description
Description:
Allow specifying the sha256 of the node binary in addition to the node version. If the asset fails to match the expected sha256, we should error.
If specifying the sha256 is not feasible, we could allow specifying the git commit of the release (https://github.com/actions/node-versions/releases).
Justification:
Ensure that any 3rd party code that runs in GitHub actions is locked down to known hashes.
Are you willing to submit a PR?
Yes, once the details are ironed out.
Contributor guide
No contributing guide indexed for this repository
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
Start with the actions/node-versions releases linked in the issue and trace how setup-node selects and downloads a Node.js asset. Define the configuration and verification behavior first; done means a supplied SHA-256 is checked and a mismatch errors, or the agreed release commit alternative is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100