chore(cyclonedx): emit metadata.tools in the 1.6 components form - #1102
Open
XiaoZ-0218 wants to merge 1 commit into
Open
chore(cyclonedx): emit metadata.tools in the 1.6 components form#1102XiaoZ-0218 wants to merge 1 commit into
XiaoZ-0218 wants to merge 1 commit into
Conversation
Replace the deprecated tools array (vendor/name/version) with tools.components using type, name, version, and publisher so the BOM stays valid when CycloneDX drops the legacy shape in 1.7. Fixes OWASP#1097
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
metadata.toolsfrom the deprecated CycloneDX 1.6 array (vendor/name/version) to the moderntools.componentsobject (type/name/version/publisher).tests/cyclonedx.test.tsso a regression back to the legacy array fails.Fixes #1097
Dependency-Track note
Issue #1097 asked to verify the documented consumer before shipping. Dependency-Track already models both legacy and component/service-based tool metadata (see DependencyTrack/dependency-track#6785: "Dependency-Track already models both legacy and component/service-based tool metadata"), so this output should remain ingestible.
Test plan