-
Notifications
You must be signed in to change notification settings - Fork 2
sbom serialNumber validation handled #195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
...ker/src/main/java/com/freenow/sauron/plugins/generator/nodejs/NodeJsDependencyGenerator.java
Outdated
Show resolved
Hide resolved
ocristian
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we also discussed removing that field from the JSON, right? Wouldn’t it be less work to simply remove it? If I remember correctly, @omidtavakoli confirmed that DependencyTrack does not require it.
|
@ocristian We discussed at the same time to generate the field in the plugin if it was including the *** to not break DependencyTrack in future if it there was an update which uses that field |
Co-authored-by: omid.tavakoli <omid.tavakoli@free-now.com>
npm sbom createa an invalid serialNumber like this "serialNumber": "urn:uuid:***" in NodeJsDependencyGenerator. This MR handles and introduces tests on the plugin