This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Scanning NPM packages prints warnings #4039
Labels
priority/backlog
Higher priority than priority/awaiting-more-evidence.
triage/support
Indicates an issue that is a support question.
Milestone
What I am trying to do
I am trying to scan a NPM monorepo with multiple
package.json
files an one top levelpackage-lock.json
for licenses.Command:
trivy fs --scanners license .
What I get as a result
Console output
What I expected
I expected Trivy to scan my dependencies and print the assessed licenses for the whole dependency graph in a table.
My setup
trivy.yaml
Project structure
. ├── README.md ├── functions │ ├── fun-1 │ │ ├── package.json │ │ ├── src │ │ └── ... │ │ └── tsconfig.json │ ├── fun-2 │ │ ├── package.json │ │ ├── src │ │ └── ... │ │ └── tsconfig.json │ └── fun-3 │ ├── package.json │ ├── src │ │ └── ... │ └── tsconfig.json ├── node_modules │ └── ... ├── package-lock.json ├── package.json ├── trivy.yaml └── tsconfig.json
My questions
package.json
files insidenode_modules
? According to the documentation for filesystem scanning this is intentionally disabled. Why? I am aware that there are A LOT of files but shouldn't the users decide how long they are willing to wait for the scan to conclude?devDependencies
. Is there a way to enable NPM dev dependency scanning and if not, why?The text was updated successfully, but these errors were encountered: