Closed ResuBaka closed 1 year ago
Any updates on this? We're experiencing this as well.
I'm having the same issue. Any update would be nice. I saw this was fixed for the vendor folder: https://github.com/aquasecurity/trivy/issues/147
This issue is stale because it has been labeled with inactivity.
A workaround for this is to utilize the --skip-dirs
flag to skip directories:
$ trivy fs . --skip-dirs node_modules
Was fixed a long time ago
Description
In version 0.19.2 only the top level yarn.lock in a project was scanned but now even the yarn.lock's from node_modules get scanned an reported. Which leads to wrong reports as the installed version of a packages is different from the one in the node_module one.
What did you expect to happen?
Do not scan node_modules yarn.lock files.
What happened instead?
Yarn.lock files are getting scanned from node_modules..
Output of run with
-debug
:Output of
trivy -v
: