You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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.
The text was updated successfully, but these errors were encountered:
There are several issues that are interfering with using
cyclonedx-bom
to write CycloneDX incargo 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: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.serialNumber
is always written, even if set toNone
. 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.output_as_json_v1_3
andoutput_as_json_v1_4
pretty-print the JSON, wasting space. Thespec
module required to implement it outsidecyclonedx-bom
is private.The text was updated successfully, but these errors were encountered: