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

Improve SBOM version resolution #410

Open
fg-j opened this issue Oct 19, 2022 · 0 comments
Open

Improve SBOM version resolution #410

fg-j opened this issue Oct 19, 2022 · 0 comments

Comments

@fg-j
Copy link

fg-j commented Oct 19, 2022

Currently, the way that packit determines which SBOM versions to generate is quite rudimentary. There is a hard-coded mapping of versions to their corresponding formats. This implementation notably lacks:

  • SemVer version parsing: the mapping looks for exact version matches only
  • support for the latest SBOM schema versions that Syft supports: we pin to specific (and sometimes outdated) schema versions
    • pinning by default is still advantageous, since changing SBOM schema between builds could be a breaking change for users, but it'd be nice to allow users to "get the latest"

We should investigate whether it's possible to learn the schema versions that a given version of Syft supports before SBOMs are generated. This could allow us to match user-requested versions with versions available directly from Syft. For instance, if a user requests a Syft SBOM version 4.* and the latest version of Syft generates version 4.1.0, we could use the upstream SBOM format rather than one of our own implementations.

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

No branches or pull requests

1 participant