fix(sbom): escape dots in spdx ids to avoid component collisions#9704
Open
ubeddulla wants to merge 1 commit into
Open
fix(sbom): escape dots in spdx ids to avoid component collisions#9704ubeddulla wants to merge 1 commit into
ubeddulla wants to merge 1 commit into
Conversation
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.
toSpdxID strips a scoped package's leading @ and turns / into ., so
@a/band an unscopeda.bboth produce SPDXRef-Package-a.b-1.0.0. spdxOutput dedupes components by that identifier, so two distinct installed packages collapse into one and a real component silently disappears from the generated SBOM, which can hide a dependency from anything that audits the SBOM. Escaping literal dots before the slash mapping keeps the identifiers distinct; CycloneDX already records the full name@version and isn't affected.