Use `npm ls --all` to resolve dependency information for NPM packages
Open
- Dominant language
- Go
- Stars
- 9.6k
- Forks
- 954
- Avg merge
- 23h 27m
- Merged PRs (30d)
- 48
Description
This issue has no description.
Contributor guide
Research direction
The issue body names no files, tests, or entry points. Start by locating Syft's NPM package dependency-resolution entry point and compare its current dependency information with the output of `npm ls --all`; done means NPM packages resolve using that complete dependency information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, node.js
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100