docs(supply-chain): require a unique top-level component name - #296
Merged
Conversation
Two submissions rejected with "already registered under a different project" even though the delivered device was different. Both times the metadata component name was a generic placeholder (a bare ".", or "/scan" from Palo Alto Networks' sbom_creator tool) that another supplier's earlier submission had already used, since the intake system treats this value as a global uniqueness key rather than a per-project one. Add the uniqueness requirement to Submission Requirements and a new rejection reason plus a worked case to Rejection Reasons (ko/en).
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.component.name(CycloneDX) /name(SPDX) held a generic placeholder value that another submission had already claimed (a bare., and/scanfrom Palo Alto Networks' officialsbom_creatortool) — the intake system treats this value as globally unique, not scoped per project.Test plan
../requirements/still resolve