trivy fs vs npm audit differs for carbone.io template engine #8285
-
DescriptionHi, I found out that commands I would expect similar/or-same output. What do you think? Thx Ivos Desired BehaviorResult number of vulnerabilites should be the same (or similar) Actual BehaviorResult number of vulnerabilites is different Reproduction Steps1. clone repository `git clone https://github.com/carboneio/carbone.git`
2. checkout tag version `git checkout ee-3.4.0`
3. run trivy scan `docker run -v /mnt/c/dev/git/carbone:/mnt/to-scan aquasec/trivy fs /mnt/to-scan`
output
...
package-lock.json (npm)
=======================
Total: 4 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 4, CRITICAL: 0)
...
Operating SystemWindows 10 WLS VersionVersion: 0.58.1 Checklist
|
Beta Was this translation helpful? Give feedback.
Answered by
DmitriyLewen
Jan 27, 2025
Replies: 1 comment 1 reply
-
Hello @bedla By default, Trivy doesn't check dev deps - https://trivy.dev/latest/docs/coverage/language/nodejs/#npm ➜ carbone git:(ee-3.4.0) trivy -q fs --include-dev-deps ./package-lock.json
package-lock.json (npm)
Total: 19 (UNKNOWN: 0, LOW: 0, MEDIUM: 3, HIGH: 13, CRITICAL: 3) |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
bedla
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello @bedla
Thanks for your report!
By default, Trivy doesn't check dev deps - https://trivy.dev/latest/docs/coverage/language/nodejs/#npm
Use
--include-dev-deps
flag to see similar result: