-
Notifications
You must be signed in to change notification settings - Fork 16
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
Cyt 615 add spdx and cyclone dx read SBOM hook implementations #221
Open
mws180000
wants to merge
19
commits into
main
Choose a base branch
from
CYT-615-Add-SPDX-and-CycloneDX-read_sbom-hook-implementations
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Cyt 615 add spdx and cyclone dx read SBOM hook implementations #221
mws180000
wants to merge
19
commits into
main
from
CYT-615-Add-SPDX-and-CycloneDX-read_sbom-hook-implementations
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…RICS observations
for more information, see https://pre-commit.ci
nightlark
added a commit
that referenced
this pull request
Jun 18, 2024
…ations' of https://github.com/LLNL/Surfactant into CYT-615-Add-SPDX-and-CycloneDX-read_sbom-hook-implementations
for more information, see https://pre-commit.ci
nightlark
added a commit
that referenced
this pull request
Jun 18, 2024
…ations' of https://github.com/LLNL/Surfactant into CYT-615-Add-SPDX-and-CycloneDX-read_sbom-hook-implementations
for more information, see https://pre-commit.ci
…ations' of https://github.com/LLNL/Surfactant into CYT-615-Add-SPDX-and-CycloneDX-read_sbom-hook-implementations
…k-implementations
In the CyTRICS schema working group I was thinking that it would be nice to be able to track what CycloneDX/SPDX identifier is associated with software entries, which would enable SBOM conversion to preserve a stable identifier for a roundtrip conversion from CycloneDX -> CyTRICS/internal -> CycloneDX. https://cyclonedx.org/capabilities/bomlink/ has an example of what a full ref looks like. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Latest working draft of the CycloneDX input SBOM hook.
This includes adding any vulnerabilities from the CycloneDX SBOM into the observations section of the CyTRICS SBOM
Change in mapping requirements: It turns out that a CycloneDX component can have nested subcomponents. Mapping these subcomponents to the components section of the CyTRICS software entry format would fit better than mapping the CycloneDX services section to the CyTRICS components section since CycloneDX services are it's won section in the SBOM (rather than being part of individual CycloneDX component entries)
Some CycloneDX-exclusive component data is currently added to the metadata section of the corresponding CyTRICS software entry, while the rest needs to be transformed into formats that are JSON-serializable