Trusted verification once moved to nodejs/
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 19
- Forks
- 15
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 2
Description
Nothing personal obviously @canterberry, but this'll need an audit by a TSC member or someone with a trust relationship to the TSC if/once it's moved, to make sure the keys are as they should be.
Flagging that now in this issue which can be closed once it's all done.
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
Review the release signing keys and the proposed nodejs/ location first. The issue requires an audit by a TSC member or someone with a trust relationship to the TSC; it is done when that audit confirms the keys are correct and the issue can be closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100