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

Provide an easy way to map an artifact to a SBOM #557

Open
lfrancke opened this issue Nov 15, 2023 · 0 comments
Open

Provide an easy way to map an artifact to a SBOM #557

lfrancke opened this issue Nov 15, 2023 · 0 comments

Comments

@lfrancke
Copy link
Contributor

A rust build can produce various artifacts in the /target folders.
The SBOMs might have different names (e.g. bom.xml or the name of the package) and it's not trivial (without parsing the SBOMs) to automatically map/match the artifact to the SBOM in question.

A second, related issue (I can split it into a separate issue) is that the metadata -> component -> name might be an "internal artifact" and not the name of the actual final product as used in the outside world (e.g. vulnerabilities might be filed against the "official" name or the "binary" name but not the package/crate name).

The "correct" name might be available as a subcomponent of metadata -> component but it's not obvious to tools which the actual thing is we're talking about (e.g. a vulnerabilty might exist in a binary but not in the library).

The only thing I can think of is to actually do create a separate SBOM file per generated artifact. That is overhead and duplication but I don't see a better way of doing this.

This was my attempt at doing this in the past and it might still be what I need: #441

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

Successfully merging a pull request may close this issue.

1 participant