Vulnerabilities for NPM Packages not populating #847
Unanswered
rohit-chaurasia
asked this question in
Q&A
Replies: 2 comments
-
According to OSS Index and NPM Audit, the components listed are not vulnerable. If you believe there are false negatives, you'll need to report them to OSS Index and the Node.js security working group. Also, note that CycloneDX v1.2 is not supported in DT 3.8.0 and prior. Support for CycloneDX v1.2 has been added in DT 4.0. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks Steve, I ended up using CycloneDX v1.0 for the BOM. I'll run a NPMAudit of the libraries manually and reverify (I have a few more than the ones listed) |
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
-
I've tried uploading a BOM using both v1.2 and v1.1 of CycloneDX however, I havent been able to get DependencyTrack to populate the vulnerabilities associated to the packages.(screenshot attached)
I'm running this out of a Docker Instance and have attached a few docker logs which I found relevant as well and was hoping you can help me figure this out.
Screenshot:
Beta Was this translation helpful? Give feedback.
All reactions