Skip to content
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

Bomber is not finding packages in a SBOM file that has been converted using the CycloneDX Convert function #171

Open
6mile opened this issue Aug 2, 2023 · 3 comments
Assignees

Comments

@6mile
Copy link

6mile commented Aug 2, 2023

The problem I am having is that bomber does NOT find any packages in a SBOM that has been converted by the cyclonedx-node covert process. The SBOM is generated from a javascript application.

To recreate for testing:
Create a CycloneDX SBOM in JSON format:
cyclonedx-node --output bomber-test.json

If we scan that SBOM with Bomber, it works:
Screenshot 2023-08-03 at 2 12 31 pm

Now convert that CycloneDX SBOM to SPDX using the cyclonedx convert function:
cat ./bomber-test.json | cyclonedx convert --input-format json --output-format spdxjson > ./converted-to-spdx.json

Now that you have a freshly converted SPDX format SBOM, run Bomber against it:
bomber scan ./converted-to-spdx.json

Unfortunately, Bomber doesn't find any packages even thought there are many components listed in the converted SBOM:
Screenshot 2023-08-02 at 3 49 11 pm

I'm attaching all files here so you can inspect them.
bomber-files.zip

@djschleen
Copy link
Member

Appreciate you attaching the files! We'll take a look.

@djschleen
Copy link
Member

@mirxcle have you taken a look yet?

@djschleen
Copy link
Member

Just touching this issue again. @mirxcle note that this is an SPDX file. I'd bet the schema isn't compatible with Bomber so we'll have to see if there's a half decent SPDX go module we can use rather than have to roll our own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants