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

Remove duplicates in cyclonedx-json format when same bom-ref #3131

Open
arkajnag23 opened this issue Aug 15, 2024 · 1 comment
Open

Remove duplicates in cyclonedx-json format when same bom-ref #3131

arkajnag23 opened this issue Aug 15, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@arkajnag23
Copy link

What would you like to be added:
Remove duplicates in cyclonedx-json format when same bom-ref

Why is this needed:
As we plan to report the json file to governance for EU and US audit, having duplicate records, feels wrong.
I understand when determining the bom-ref, we are adding a package-id for making it unique for a library, but can't we remove that and
add within the properties with multiple json objects showing the source of the package.

               {
                    "name": "source",
                    "value": "<path 1>"
                },
                {
                    "name": "source",
                    "value": "<path 2>"
                }

Additional context:

@arkajnag23 arkajnag23 added the enhancement New feature or request label Aug 15, 2024
@willmurphyscode
Copy link
Contributor

Hi @arkajnag23,

Could you help us understand this problem a little bit more specifically? The JSON you included isn't enough information for me to understand what the problem is. Which fields are being duplicated?

My recommendation is to scan a publicly available Docker image (so you don't have any confidentiality concerns on posting it) and attach a cyclonedx-json output to this issue, and discuss what information is duplicated in order to illustrate the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

3 participants