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

cyclonedx-bom is unsuitable for cargo auditable use case #628

Open
4 tasks
Shnatsel opened this issue Feb 24, 2024 · 0 comments
Open
4 tasks

cyclonedx-bom is unsuitable for cargo auditable use case #628

Shnatsel opened this issue Feb 24, 2024 · 0 comments

Comments

@Shnatsel
Copy link
Contributor

Shnatsel commented Feb 24, 2024

There are several issues that are interfering with using cyclonedx-bom to write CycloneDX in cargo auditable

cargo auditable operates under very different constraints to regular SBOMs; this is what drove me to use a custom format as opposed to using an off-the-shelf CycloneDX or SPDX. The issues currently affecting it are:

  • Toplevel version has been made a required field in Update 'version' to be required field #618 and is always written. It needs to be omitted to save bytes.
  • Toplevel serialNumber is always written, even if set to None. It needs to be omitted to save bytes.
  • dependencies.dependsOn is always written, even if empty. It should be omitted when empty to save bytes.
  • There is no way to write a minified JSON. output_as_json_v1_3 and output_as_json_v1_4 pretty-print the JSON, wasting space. The spec module required to implement it outside cyclonedx-bom is private.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant