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

Add support for determining supplier of packages #1961

Open
kzantow opened this issue Jul 26, 2023 · 2 comments
Open

Add support for determining supplier of packages #1961

kzantow opened this issue Jul 26, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@kzantow
Copy link
Contributor

kzantow commented Jul 26, 2023

What would you like to be added:
The supplier field to SBOMs, in order to conform to the NITA minimum SBOM requirements.

Why is this needed:
Syft should generate SBOMs that include the NTIA minimum requirements. The supplier field is one aspect of the NITA minimum SBOM requirements which Syft is not currently populating.

Additional context:
This is an aspect of #632

@spiffcs
Copy link
Contributor

spiffcs commented Aug 1, 2023

Part of the next step of this work after #1980 goes in is keying off of the example of when the originator and the supplier are different and how to read that into documents that are not handcrafted - what package manager fields/data exist to allow us to make this distinction across ecosystems on document generation

The SPDX document identifies the package as [glibc](https://www.gnu.org/software/libc/) 
and the Package Supplier as [Red Hat](https://www.redhat.com/), 
but the [Free Software Foundation](http://www.fsf.org/) is the Package Originator.

@kzantow
Copy link
Contributor Author

kzantow commented Aug 1, 2023

We also need to be able to provide a supplier to the "source", which ends up as root elements in SPDX and CycloneDX. One possibility is to add something like --source-name and --source-version, which could be --source-supplier, but we don't have this element in the Syft data model yet, so it would need to be added. It is possible this supplier information should then be used for packages as well (e.g. who should a user contact when they need something done to the software to correct an issue/vulnerability/etc.). It might also be important to add something to a "hints" file to be able to be more specific about overriding/specifying information for specific packages.

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