Replies: 2 comments
-
I have verified that same behaviour exits at latest version of trivy: Version: 0.55.1 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hello @gobardhan Trivy's current logic is: Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
As per the trivy documentation
By default, Trivy doesn't report development dependencies
So ideally no vulnerability should be highlighted related to Development dependencies neither for the extraneous packages which are related to development dependencies.Desired Behavior
Running trivy fs command (without flag --include-dev-deps) should not scan any extraneous (indirect) dependencies which are related to development dependencies
Actual Behavior
Running trivy fs command scans those indirect dependencies which are marked as extraneous in package-lock.json like:
"node_modules/@salesforce/cli/node_modules/@aws-sdk/client-cloudfront/node_modules/fast-xml-parser": { "version": "4.2.5", "resolved": "https://registry.npmjs.org/fast-xml-parser/-/fast-xml-parser-4.2.5.tgz", "extraneous": true,
Reproduction Steps
Target
Filesystem
Scanner
None
Output Format
None
Mode
Standalone
Debug Output
Operating System
Ubuntu 22.04.4 LTS
Version
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions