-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
[Dependency-Track integration] JSON BOM upload fails with Dependency Track 4.2.2 #53
Comments
@mattwongsd Thank you filing this defect. Looks like the name attribute is duplicated possibly because we are getting an object instead of a string here https://github.com/AppThreat/cdxgen/blob/master/index.js#L94 Could you kindly send a PR so that we hardcode the name to resolve this issue? |
On locally the structure looks fine so I'm confused a bit. Could you share the node version used? Also, cdxgen can upload directly to dependency track. Is that something you could try as well when you get a chance? |
@mattwongsd any updates regarding this? |
The upload to DT does not work. I do not get any feedback when I provided the command arguments, |
@mattwongsd Any luck with the new version? Once this works, I might ask for your help to replace use of |
Is there any update on this issue? After generate a SBoM for a multi module gradle project with java, npm, python and some other stuff i got a SBoM containing all dependencies of the project, but if i upload the SBoM to Dependeny Track we got the following dependency server log message:
Using Dependency Track 4.8.2 and cdxgen latest docker image. EDIT: |
@thaarbach Downstream tools like dependency-track are yet to be updated to cyclonedx 1.5. The error https://github.com/CycloneDX/cdxgen/blob/master/bin/cdxgen.js#L157 |
Steps:
I suspect that the authors field is causing the error.
I've also tried uploading the raw JSON BOM via the web UI and encountered the same issue.
When I removed the authors field from the BOM, everything seems to be working fine.
The text was updated successfully, but these errors were encountered: