audit does not report the top level module to which a vulnerability was related.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
npcheck should at least show the top level module that pulled in a module with a reported CVE. Ideally the tree would be even better.
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
No files or tests are named. Start by locating npcheck's audit output and dependency-resolution entry points, then trace how a reported CVE is associated with its dependency tree. Done means the audit identifies the top-level module that brought in the vulnerable module; the requested full tree is described as optional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100