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

Investigate if custom registries should result in purl's with a different type from "cargo" #231

Open
amy-keibler opened this issue Aug 21, 2022 · 1 comment
Labels
cargo-cyclonedx Issues related to the Cargo SBOM generation application enhancement New feature or request

Comments

@amy-keibler
Copy link
Collaborator

From #226's

  1. Is the purl standardized for Rust somewhere in the spec? What should the purl be for crates not distributed via crates.io?

The purl specification does not indicate a required type specific to Rust, beyond

type: the package "type" or package "protocol" such as maven, npm, nuget, gem, pypi, etc. Required.

Investigate what other CycloneDX tools are doing, particularly if they support private repositories. Rust supports private registries and indicates at a per-dependency level what registry it comes from, so we should be able to access this information if we want to use that as the purl's type for a dependency component and the [package]'s publish list for the package's component

@amy-keibler amy-keibler added enhancement New feature or request cargo-cyclonedx Issues related to the Cargo SBOM generation application labels Aug 21, 2022
@Shnatsel
Copy link
Contributor

Shnatsel commented Nov 3, 2023

There is a dedicated qualifier for this:

repository_url is an extra URL for an alternative, non-default package repository or registry.

Source: https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst#known-qualifiers-keyvalue-pairs

This is what is used in #523

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cargo-cyclonedx Issues related to the Cargo SBOM generation application enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants