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

Switch from packageurl to purl crate #636

Open
Shnatsel opened this issue Feb 29, 2024 · 0 comments
Open

Switch from packageurl to purl crate #636

Shnatsel opened this issue Feb 29, 2024 · 0 comments
Labels
cyclonedx-bom Issues related to the specification library implementation

Comments

@Shnatsel
Copy link
Contributor

Currently cyclonedx-bom relies on packageurl crate, which does not support important fields such as qualifiers (e.g. ?vcs_url=... so that we could encode repo URLs for git dependencies), and the last release of packageurl has been 2 years ago.

The purl crate is a lot more complete and is actively maintained. The maintainers aren't afraid of tackling tough issues across the whole PURL ecosystem that require changes to the spec. (Naturally, spec authors ignore their PRs, but it's the thought that counts!)

cargo cyclonedx already depends on purl to compose the actual PURLs and then converts them to packageurl to feed them to cyclonedx-bom. We should migrate cyclonedx-bom itself to purl crate as well, since the packageurl is woefully insufficient even for our own use cases and that is not going to change anytime soon.

@Shnatsel Shnatsel added the cyclonedx-bom Issues related to the specification library implementation label Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cyclonedx-bom Issues related to the specification library implementation
Projects
None yet
Development

No branches or pull requests

1 participant