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

[PROPOSAL] Standardized cdx namespace property for source file #28

Open
candrews opened this issue Sep 30, 2022 · 2 comments
Open

[PROPOSAL] Standardized cdx namespace property for source file #28

candrews opened this issue Sep 30, 2022 · 2 comments
Labels

Comments

@candrews
Copy link

The cdx namespace should include a property to hold the path of the file that produced the dependency.

Vendors have started included such a property in their namespaces; the lack of standardization around the storage of this information is creating a significant interoperability problem.

For example, GitLab uses gitlab:dependency_scanning:input_file:path.

If this property is standardized, other SBOM producing tools will be more likely to include this information, and SBOM consumers will more likely use it.

@candrews
Copy link
Author

candrews commented Oct 1, 2022

Seems related to CycloneDX/specification#31

@coderpatros
Copy link
Member

Hi @candrews, this is something we are planning to address in the core spec in v1.5.

@jkowalleck jkowalleck added TLN-registration registration of a Top Level Namespace idea and removed TLN-registration registration of a Top Level Namespace labels Jun 7, 2023
@jkowalleck jkowalleck changed the title Standardized cdx namespace property for source file [PROPOSAL] Standardized cdx namespace property for source file Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants