nodejs / nodejs/nodejs-dependency-vuln-assessments
Recursive support on Node.js dependencies
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 22
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Yes, we've discussed it in the last Security WG meeting. We agreed on testing the recursive approach, and in case it adds a lot of noise, we revert it.
Originally posted by @RafaelGSS in https://github.com/nodejs/nodejs-dependency-vuln-assessments/issues/88#issuecomment-1314034102
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 reading the discussion referenced from issue #88 and the Security WG decision recorded here. Determine how recursive dependency assessment should be tested and what constitutes unacceptable noise; done means the recursive approach has been evaluated and either retained or reverted based on that result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100