migration of untransferred npm packages to nodejs-foundation account
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
Some NPM packages belonging to this organization are not under the nodejs-foundation NPM account. It would be good for the following packages to be under that account's domain:
- amaro
- is-my-node-vulnerable
- undici
- nodejs-cve-checker
- llhttp
- nodejs-dist-indexer
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
Start by reviewing the referenced nodejs.org pull request and the ownership of the six listed npm packages: amaro, is-my-node-vulnerable, undici, nodejs-cve-checker, llhttp, and nodejs-dist-indexer. Done means each package is transferred to or managed under the nodejs-foundation npm account; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100