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

Enabling SBOM across repositories #33

Open
codeboten opened this issue Nov 15, 2023 · 9 comments
Open

Enabling SBOM across repositories #33

codeboten opened this issue Nov 15, 2023 · 9 comments
Assignees
Labels
sbom Items related to questions, best practices, and recommendations for SBOMs

Comments

@codeboten
Copy link
Contributor

This issue is to capture discussions happening in various SIGs around creating a software bill of materials.

@codeboten
Copy link
Contributor Author

@ocelotl
Copy link

ocelotl commented Nov 22, 2023

There seems to be at least 3 SBOM formats. We probably should decide on which one we want to use first.

@mlieberman85
Copy link

SWIDs claim to be an SBOM format but are more of an identifier format, but also not really a great solution there. Realistically the decision really is between SPDX and CycloneDX, though they are mostly interchangeable unless you have a very specific use case. My perspective comes from CNCF TAG Security, work with OpenSSF and work with SPDX community.

If folks are interested I can pull in experts to discuss with your community.

@ocelotl
Copy link

ocelotl commented Nov 22, 2023

Just for the record, I used syft and cyclonedx-py to generate SBOMs for the OTel Python opentelemetry-sdk package in SPDX and CycloneDX formats.

@ocelotl
Copy link

ocelotl commented Nov 22, 2023

SWIDs claim to be an SBOM format but are more of an identifier format, but also not really a great solution there. Realistically the decision really is between SPDX and CycloneDX, though they are mostly interchangeable unless you have a very specific use case. My perspective comes from CNCF TAG Security, work with OpenSSF and work with SPDX community.

If folks are interested I can pull in experts to discuss with your community.

I am interested ✌️, which is this use case you mention above, @mlieberman85?

@codeboten
Copy link
Contributor Author

If folks are interested I can pull in experts to discuss with your community.

This would be great @mlieberman85!

@mlieberman85
Copy link

SWIDs claim to be an SBOM format but are more of an identifier format, but also not really a great solution there. Realistically the decision really is between SPDX and CycloneDX, though they are mostly interchangeable unless you have a very specific use case. My perspective comes from CNCF TAG Security, work with OpenSSF and work with SPDX community.
If folks are interested I can pull in experts to discuss with your community.

I am interested ✌️, which is this use case you mention above, @mlieberman85?

So the use cases where they're not right now are mostly focused on specific fields that might be in one but not the other. For example there's AI/ML model specific bill of materials fields in CycloneDX released already, and a similar SPDX feature is still being developed.

Let me reach out to some of the folks in the community and tag them in this thread.

@mlieberman85
Copy link

Adding @puerco who is an expert in the community.

@puerco
Copy link

puerco commented Nov 24, 2023

Hello happy to help out! Do you have a tracker of projects that need to build their SBOMs?

@jpkrohling jpkrohling self-assigned this Jul 3, 2024
@jpkrohling jpkrohling added the sbom Items related to questions, best practices, and recommendations for SBOMs label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sbom Items related to questions, best practices, and recommendations for SBOMs
Projects
None yet
Development

No branches or pull requests

5 participants