Specifies the format of the BOM. This helps to identify the file as CycloneDX since BOMs do not have a filename convention nor does JSON schema support namespaces. This value MUST be "CycloneDX".
The version of the CycloneDX specification a BOM conforms to (starting at version 1.2).
"1.5"
Every BOM generated SHOULD have a unique serial number, even if the contents of the BOM have not changed over time. If specified, the serial number MUST conform to RFC-4122. Use of serial numbers are RECOMMENDED.
Must match regular expression:^urn:uuid:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$ "urn:uuid:3e671687-395b-41f5-a30f-a58921a69b79"
Whenever an existing BOM is modified, either manually or through automated processes, the version of the BOM SHOULD be incremented by 1. When a system is presented with multiple BOMs with identical serial numbers, the system SHOULD use the most recent version of the BOM. The default version is '1'.
Value must be greater or equal to 1
1
Provides additional information about a BOM.
No Additional PropertiesThe date and time (timestamp) when the BOM was created.
The product lifecycle(s) that this BOM represents.
A pre-defined phase in the product lifecycle.
The name of the lifecycle phase
The description of the lifecycle phase
The tool(s) used in the creation of the BOM.
No Additional PropertiesA list of software and hardware components used as tools
All items must be unique
No Additional ItemsSpecifies the type of component. For software components, classify as application if no more specific appropriate classification is available or cannot be determined for the component. Types include:
"library"
The optional mime-type of the component. When used on file components, the mime-type can provide additional context about the kind of file being represented such as an image, font, or executable. Some library or framework components may also have an associated mime-type.
Must match regular expression:^[-+a-z0-9.]+/[-+a-z0-9.]+$ "image/jpeg"
An optional identifier which can be used to reference the component elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The organization that supplied the component. The supplier may often be the manufacturer, but may also be a distributor or repackager.
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The person(s) or organization(s) that published the component
"Acme Inc"
The grouping name or identifier. This will often be a shortened, single name of the company or project that produced the component, or the source package or domain name. Whitespace and special characters should be avoided. Examples include: apache, org.apache.commons, and apache.org.
"com.acme"
The name of the component. This will often be a shortened, single name of the component. Examples: commons-lang3 and jquery
"tomcat-catalina"
The component version. The version should ideally comply with semantic versioning but is not enforced.
"9.0.14"
Specifies a description for the component
Specifies the scope of the component. If scope is not specified, 'required' scope SHOULD be assumed by the consumer of the BOM.
^([a-fA-F0-9]{32}|[a-fA-F0-9]{40}|[a-fA-F0-9]{64}|[a-fA-F0-9]{96}|[a-fA-F0-9]{128})$ "3942447fac867ae5cdb3229b658f4d48"
EITHER (list of SPDX licenses and/or named licenses) OR (tuple of one SPDX License Expression)
A list of SPDX licenses and/or named licenses.
No Additional ItemsAn optional identifier which can be used to reference the license elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
A valid SPDX license ID
"Apache-2.0"
If SPDX does not define the license used, this field may be used to provide the license name
"Acme Software License"
An optional way to include the textual content of a license.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
The URL to the license file. If specified, a 'license' externalReference should also be specified for completeness
"https://www.apache.org/licenses/LICENSE-2.0.txt"
Licensing details describing the licensor/licensee, license type, renewal and expiration dates, and other important metadata
No Additional PropertiesLicense identifiers that may be used to manage licenses and their lifecycle
No Additional ItemsThe individual or organization that grants a license to another individual or organization
No Additional PropertiesThe organization that granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual, not associated with an organization, that granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual or organization for which a license was granted to
No Additional PropertiesThe organization that was granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual, not associated with an organization, that was granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual or organization that purchased the license
No Additional PropertiesThe organization that purchased the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual, not associated with an organization, that purchased the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The purchase order identifier the purchaser sent to a supplier or vendor to authorize a purchase
The type of license(s) that was granted to the licensee
The timestamp indicating when the license was last renewed. For new purchases, this is often the purchase or acquisition date. For non-perpetual licenses or subscriptions, this is the timestamp of when the license was last renewed.
The timestamp indicating when the current license expires (if applicable).
Provides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
No Additional ItemsProvides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
The name of the property. Duplicate names are allowed, each potentially having a different value.
The value of the property.
A tuple of exactly one SPDX License Expression.
Must contain a minimum of 1 items
Must contain a maximum of 1 items
"Apache-2.0 AND (MIT OR GPL-2.0-only)"
"GPL-3.0-only WITH Classpath-exception-2.0"
An optional identifier which can be used to reference the license elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
A copyright notice informing users of the underlying claims to copyright ownership in a published work.
"Acme Inc"
Specifies a well-formed CPE name that conforms to the CPE 2.2 or 2.3 specification. See https://nvd.nist.gov/products/cpe
"cpe:2.3:a:acme:component_framework:-:*:*:*:*:*:*:*"
Specifies the package-url (purl). The purl, if specified, MUST be valid and conform to the specification defined at: https://github.com/package-url/purl-spec
"pkg:maven/com.acme/[email protected]?packaging=jar"
Specifies metadata and content for ISO-IEC 19770-2 Software Identification (SWID) Tags.
No Additional PropertiesMaps to the tagId of a SoftwareIdentity.
Maps to the name of a SoftwareIdentity.
Maps to the version of a SoftwareIdentity.
Maps to the tagVersion of a SoftwareIdentity.
Maps to the patch of a SoftwareIdentity.
Specifies the metadata and content of the SWID tag.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
The URL to the SWID file.
[Deprecated] - DO NOT USE. This will be removed in a future version. Use the pedigree element instead to supply information on exactly how the component was modified. A boolean value indicating if the component has been modified from the original. A value of true indicates the component is a derivative of the original. A value of false indicates the component has not been modified from the original.
Component pedigree is a way to document complex supply chain scenarios where components are created, distributed, modified, redistributed, combined with other components, etc. Pedigree supports viewing this complex chain from the beginning, the end, or anywhere in the middle. It also provides a way to document variants where the exact relation may not be known.
No Additional PropertiesDescribes zero or more components in which a component is derived from. This is commonly used to describe forks from existing projects where the forked version contains a ancestor node containing the original component it was forked from. For example, Component A is the original component. Component B is the component being used and documented in the BOM. However, Component B contains a pedigree node with a single ancestor documenting Component A - the original component from which Component B is derived from.
No Additional ItemsDescendants are the exact opposite of ancestors. This provides a way to document all forks (and their forks) of an original or root component.
No Additional ItemsVariants describe relations where the relationship between the components are not known. For example, if Component A contains nearly identical code to Component B. They are both related, but it is unclear if one is derived from the other, or if they share a common ancestor.
No Additional ItemsA list of zero or more commits which provide a trail describing how the component deviates from an ancestor, descendant, or variant.
No Additional ItemsSpecifies an individual commit
No Additional PropertiesA unique identifier of the commit. This may be version control specific. For example, Subversion uses revision numbers whereas git uses commit hashes.
The URL to the commit. This URL will typically point to a commit in a version control system.
The person who committed or pushed the commit
No Additional PropertiesThe timestamp in which the action occurred
The name of the individual who performed the action
The email address of the individual who performed the action
The text description of the contents of the commit
No Additional ItemsA list of zero or more patches describing how the component deviates from an ancestor, descendant, or variant. Patches may be complimentary to commits or may be used in place of commits.
Specifies an individual patch
No Additional PropertiesSpecifies the purpose for the patch including the resolution of defects, security issues, or new behavior or functionality.
The patch file (or diff) that show changes. Refer to https://en.wikipedia.org/wiki/Diff
No Additional PropertiesSpecifies the optional text of the diff
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
Specifies the URL to the diff
A collection of issues the patch resolves
No Additional ItemsAn individual issue that has been resolved.
No Additional PropertiesSpecifies the type of issue
The identifier of the issue assigned by the source of the issue
The name of the issue
A description of the issue
The source of the issue where it is documented
No Additional PropertiesThe name of the source. For example 'National Vulnerability Database', 'NVD', and 'Apache'
The url of the issue documentation as provided by the source
A collection of URL's for reference. Multiple URLs are allowed.
No Additional Items"https://example.com"
Notes, observations, and other non-structured commentary describing the components pedigree.
External references provide a way to document systems, sites, and information that may be relevant, but are not included with the BOM. They may also establish specific relationships within or external to the BOM.
No Additional ItemsExternal references provide a way to document systems, sites, and information that may be relevant, but are not included with the BOM. They may also establish specific relationships within or external to the BOM.
No Additional PropertiesThe URI (URL or URN) to the external reference. External references are URIs and therefore can accept any URL scheme including https (RFC-7230), mailto (RFC-2368), tel (RFC-3966), and dns (RFC-4501). External references may also include formally registered URNs such as CycloneDX BOM-Link to reference CycloneDX BOMs or any object within a BOM. BOM-Link transforms applicable external references into relationships that can be expressed in a BOM or across BOMs.
Descriptor for another BOM document. See https://cyclonedx.org/capabilities/bomlink/
Must match regular expression:^urn:cdx:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/[1-9][0-9]*$ Descriptor for an element in a BOM document. See https://cyclonedx.org/capabilities/bomlink/
Must match regular expression:^urn:cdx:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/[1-9][0-9]*#.+$ An optional comment describing the external reference
Specifies the type of external reference.
The hashes of the external reference (if applicable).
No Additional Items^([a-fA-F0-9]{32}|[a-fA-F0-9]{40}|[a-fA-F0-9]{64}|[a-fA-F0-9]{96}|[a-fA-F0-9]{128})$ "3942447fac867ae5cdb3229b658f4d48"
A list of software and hardware components included in the parent component. This is not a dependency tree. It provides a way to specify a hierarchical representation of component assemblies, similar to system → subsystem → parts assembly in physical supply chains.
All items must be unique
No Additional ItemsProvides the ability to document evidence collected through various forms of extraction or analysis.
No Additional PropertiesEvidence that substantiates the identity of a component.
No Additional PropertiesThe identity field of the component which the evidence describes.
The overall confidence of the evidence from 0 - 1, where 1 is 100% confidence.
Value must be greater or equal to 0 and lesser or equal to 1
The methods used to extract and/or analyze the evidence.
No Additional ItemsThe technique used in this method of analysis.
The confidence of the evidence from 0 - 1, where 1 is 100% confidence. Confidence is specific to the technique used. Each technique of analysis can have independent confidence.
Value must be greater or equal to 0 and lesser or equal to 1
The value or contents of the evidence.
The object in the BOM identified by its bom-ref. This is often a component or service, but may be any object type supporting bom-refs. Tools used for analysis should already be defined in the BOM, either in the metadata/tools, components, or formulation.
All items must be unique
No Additional ItemsDescriptor for an element identified by the attribute 'bom-ref' in the same BOM document.
In contrast to bomLinkElementType.
Must be at least 1 characters long
Descriptor for an element in a BOM document. See https://cyclonedx.org/capabilities/bomlink/
Must match regular expression:^urn:cdx:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/[1-9][0-9]*#.+$ Evidence of individual instances of a component spread across multiple locations.
No Additional ItemsAn optional identifier which can be used to reference the occurrence elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The location or path to where the component was found.
Evidence of the components use through the callstack.
No Additional PropertiesA package organizes modules into namespaces, providing a unique namespace for each type it contains.
A module or class that encloses functions/methods and other code.
A block of code designed to perform a particular task.
Optional arguments that are passed to the module or function.
No Additional ItemsThe line number the code that is called resides on.
The column the code that is called resides.
The full path and filename of the module.
EITHER (list of SPDX licenses and/or named licenses) OR (tuple of one SPDX License Expression)
A list of SPDX licenses and/or named licenses.
No Additional ItemsAn optional identifier which can be used to reference the license elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
A valid SPDX license ID
"Apache-2.0"
If SPDX does not define the license used, this field may be used to provide the license name
"Acme Software License"
An optional way to include the textual content of a license.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
The URL to the license file. If specified, a 'license' externalReference should also be specified for completeness
"https://www.apache.org/licenses/LICENSE-2.0.txt"
Licensing details describing the licensor/licensee, license type, renewal and expiration dates, and other important metadata
No Additional PropertiesLicense identifiers that may be used to manage licenses and their lifecycle
No Additional ItemsThe individual or organization that grants a license to another individual or organization
No Additional PropertiesThe organization that granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual, not associated with an organization, that granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual or organization for which a license was granted to
No Additional PropertiesThe organization that was granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual, not associated with an organization, that was granted the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual or organization that purchased the license
No Additional PropertiesThe organization that purchased the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The individual, not associated with an organization, that purchased the license
No Additional PropertiesAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
The purchase order identifier the purchaser sent to a supplier or vendor to authorize a purchase
The type of license(s) that was granted to the licensee
The timestamp indicating when the license was last renewed. For new purchases, this is often the purchase or acquisition date. For non-perpetual licenses or subscriptions, this is the timestamp of when the license was last renewed.
The timestamp indicating when the current license expires (if applicable).
Provides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
No Additional ItemsProvides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
The name of the property. Duplicate names are allowed, each potentially having a different value.
The value of the property.
A tuple of exactly one SPDX License Expression.
Must contain a minimum of 1 items
Must contain a maximum of 1 items
"Apache-2.0 AND (MIT OR GPL-2.0-only)"
"GPL-3.0-only WITH Classpath-exception-2.0"
An optional identifier which can be used to reference the license elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
Specifies optional release notes.
No Additional PropertiesThe software versioning type the release note describes.
"major"
"minor"
"patch"
"pre-release"
"internal"
The title of the release.
The URL to an image that may be prominently displayed with the release note.
A short description of the release.
The date and time (timestamp) when the release note was created.
One or more alternate names the release may be referred to. This may include unofficial terms used by development and marketing teams (e.g. code names).
No Additional ItemsA collection of issues that have been resolved.
No Additional ItemsAn individual issue that has been resolved.
No Additional PropertiesSpecifies the type of issue
The identifier of the issue assigned by the source of the issue
The name of the issue
A description of the issue
The source of the issue where it is documented
No Additional PropertiesThe name of the source. For example 'National Vulnerability Database', 'NVD', and 'Apache'
The url of the issue documentation as provided by the source
A collection of URL's for reference. Multiple URLs are allowed.
No Additional Items"https://example.com"
Zero or more release notes containing the locale and content. Multiple note objects may be specified to support release notes in a wide variety of languages.
No Additional ItemsA note containing the locale and content.
No Additional PropertiesThe ISO-639 (or higher) language code and optional ISO-3166 (or higher) country code. Examples include: "en", "en-US", "fr" and "fr-CA"
Must match regular expression:^([a-z]{2})(-[A-Z]{2})?$ Specifies the full content of the release note.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
Provides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
No Additional ItemsProvides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
The name of the property. Duplicate names are allowed, each potentially having a different value.
The value of the property.
A model card describes the intended uses of a machine learning model and potential limitations, including biases and ethical considerations. Model cards typically contain the training parameters, which datasets were used to train the model, performance metrics, and other relevant data useful for ML transparency. This object SHOULD be specified for any component of type machine-learning-model and MUST NOT be specified for other component types.
An optional identifier which can be used to reference the model card elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
Hyper-parameters for construction of the model.
No Additional PropertiesThe overall approach to learning used by the model for problem solving.
No Additional PropertiesLearning types describing the learning problem or hybrid learning problem.
Directly influences the input and/or output. Examples include classification, regression, clustering, etc.
The model architecture family such as transformer network, convolutional neural network, residual neural network, LSTM neural network, etc.
The specific architecture of the model such as GPT-1, ResNet-50, YOLOv3, etc.
The datasets used to train and evaluate the model.
No Additional ItemsAn optional identifier which can be used to reference the dataset elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The general theme or subject matter of the data being specified.
The name of the dataset.
The contents or references to the contents of the data being described.
No Additional PropertiesAn optional way to include textual or encoded data.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
The URL to where the data can be retrieved.
Provides the ability to document name-value parameters used for configuration.
No Additional ItemsProvides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
The name of the property. Duplicate names are allowed, each potentially having a different value.
The value of the property.
Data classification tags data according to its type, sensitivity, and value if altered, stolen, or destroyed.
A description of any sensitive data in a dataset.
No Additional ItemsA collection of graphics that represent various measurements.
No Additional PropertiesA description of this collection of graphics.
A collection of graphics.
No Additional ItemsThe name of the graphic.
The graphic (vector or raster). Base64 encoding MUST be specified for binary images.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
A description of the dataset. Can describe size of dataset, whether it's used for source code, training, testing, or validation, etc.
Data custodians are responsible for the safe custody, transport, and storage of data.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
An optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
Data stewards are responsible for data content, context, and associated business rules.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
An optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
Data owners are concerned with risk and appropriate access to data.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
An optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
References a data component by the components bom-ref attribute
Descriptor for an element identified by the attribute 'bom-ref' in the same BOM document.
In contrast to bomLinkElementType.
Must be at least 1 characters long
Descriptor for an element in a BOM document. See https://cyclonedx.org/capabilities/bomlink/
Must match regular expression:^urn:cdx:[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}/[1-9][0-9]*#.+$ The input format(s) of the model
No Additional ItemsThe data format for input/output to the model. Example formats include string, image, time-series
The output format(s) from the model
No Additional ItemsThe data format for input/output to the model. Example formats include string, image, time-series
A quantitative analysis of the model
No Additional PropertiesThe model performance metrics being reported. Examples may include accuracy, F1 score, precision, top-3 error rates, MSC, etc.
No Additional ItemsThe type of performance metric.
The value of the performance metric.
The name of the slice this metric was computed on. By default, assume this metric is not sliced.
The confidence interval of the metric.
No Additional PropertiesThe lower bound of the confidence interval.
The upper bound of the confidence interval.
A collection of graphics that represent various measurements.
No Additional PropertiesA description of this collection of graphics.
A collection of graphics.
No Additional ItemsThe name of the graphic.
The graphic (vector or raster). Base64 encoding MUST be specified for binary images.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
What considerations should be taken into account regarding the model's construction, training, and application?
No Additional PropertiesWho are the intended users of the model?
No Additional ItemsWhat are the intended use cases of the model?
No Additional ItemsWhat are the known technical limitations of the model? E.g. What kind(s) of data should the model be expected not to perform well on? What are the factors that might degrade model performance?
No Additional ItemsWhat are the known tradeoffs in accuracy/performance of the model?
No Additional ItemsWhat are the ethical (or environmental) risks involved in the application of this model?
No Additional ItemsThe name of the risk.
Strategy used to address this risk.
How does the model affect groups at risk of being systematically disadvantaged? What are the harms and benefits to the various affected groups?
No Additional ItemsInformation about the benefits and harms of the model to an identified at risk group.
No Additional PropertiesThe groups or individuals at risk of being systematically disadvantaged by the model.
Expected benefits to the identified groups.
Expected harms to the identified groups.
With respect to the benefits and harms outlined, please describe any mitigation strategy implemented.
Provides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
No Additional ItemsProvides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
The name of the property. Duplicate names are allowed, each potentially having a different value.
The value of the property.
This object SHOULD be specified for any component of type data and MUST NOT be specified for other component types.
An optional identifier which can be used to reference the dataset elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The general theme or subject matter of the data being specified.
The name of the dataset.
The contents or references to the contents of the data being described.
No Additional PropertiesAn optional way to include textual or encoded data.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
The URL to where the data can be retrieved.
Provides the ability to document name-value parameters used for configuration.
No Additional ItemsProvides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
The name of the property. Duplicate names are allowed, each potentially having a different value.
The value of the property.
Data classification tags data according to its type, sensitivity, and value if altered, stolen, or destroyed.
A description of any sensitive data in a dataset.
No Additional ItemsA collection of graphics that represent various measurements.
No Additional PropertiesA description of this collection of graphics.
A collection of graphics.
No Additional ItemsThe name of the graphic.
The graphic (vector or raster). Base64 encoding MUST be specified for binary images.
No Additional PropertiesSpecifies the content type of the text. Defaults to text/plain if not specified.
Specifies the optional encoding the text is represented in.
The attachment data. Proactive controls such as input validation and sanitization should be employed to prevent misuse of attachment text.
A description of the dataset. Can describe size of dataset, whether it's used for source code, training, testing, or validation, etc.
Data custodians are responsible for the safe custody, transport, and storage of data.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
An optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
Data stewards are responsible for data content, context, and associated business rules.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
An optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
Data owners are concerned with risk and appropriate access to data.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of the organization
"Example Inc."
The URL of the organization. Multiple URLs are allowed.
No Additional Items"https://example.com"
A contact at the organization. Multiple contacts are allowed.
No Additional ItemsAn optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
An optional identifier which can be used to reference the object elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Must be at least 1 characters long
The name of a contact
"Contact name"
The phone number of the contact.
"800-555-1212"
Provides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
No Additional ItemsProvides the ability to document properties in a name-value store. This provides flexibility to include data not officially supported in the standard without having to use additional namespaces or create extensions. Unlike key-value stores, properties support duplicate names, each potentially having different values. Property names of interest to the general public are encouraged to be registered in the CycloneDX Property Taxonomy. Formal registration is OPTIONAL.
The name of the property. Duplicate names are allowed, each potentially having a different value.
The value of the property.
Enveloped signature in JSON Signature Format (JSF).
Unique top level property for Multiple Signatures. (multisignature)
No Additional ItemsSignature algorithm. The currently recognized JWA [RFC7518] and RFC8037 [RFC8037] asymmetric key algorithms. Note: Unlike RFC8037 [RFC8037] JSF requires explicit Ed* algorithm names instead of "EdDSA".
Signature algorithm. Note: If proprietary signature algorithms are added, they must be expressed as URIs.
Optional. Application specific string identifying the signature key.
Optional. Public key object.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"EC" Key type indicator.
EC curve name.
EC curve point X. The length of this field must be the full size of a coordinate for the curve specified in the "crv" parameter. For example, if the value of "crv" is "P-521", the decoded argument must be 66 bytes.
EC curve point Y. The length of this field must be the full size of a coordinate for the curve specified in the "crv" parameter. For example, if the value of "crv" is "P-256", the decoded argument must be 32 bytes.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"OKP" Key type indicator.
EdDSA curve name.
EdDSA curve point X. The length of this field must be the full size of a coordinate for the curve specified in the "crv" parameter. For example, if the value of "crv" is "Ed25519", the decoded argument must be 32 bytes.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"RSA" Key type indicator.
RSA modulus.
RSA exponent.
Key type indicator.
Additional Properties of any type are allowed.
Type: objectOptional. Sorted array of X.509 [RFC5280] certificates, where the first element must contain the signature certificate. The certificate path must be contiguous but is not required to be complete.
No Additional ItemsOptional. Array holding the names of one or more application level properties that must be excluded from the signature process. Note that the "excludes" property itself, must also be excluded from the signature process. Since both the "excludes" property and the associated data it points to are unsigned, a conforming JSF implementation must provide options for specifying which properties to accept.
No Additional ItemsThe signature data. Note that the binary representation must follow the JWA [RFC7518] specifications.
Unique top level property for Signature Chains. (signaturechain)
No Additional ItemsSignature algorithm. The currently recognized JWA [RFC7518] and RFC8037 [RFC8037] asymmetric key algorithms. Note: Unlike RFC8037 [RFC8037] JSF requires explicit Ed* algorithm names instead of "EdDSA".
Signature algorithm. Note: If proprietary signature algorithms are added, they must be expressed as URIs.
Optional. Application specific string identifying the signature key.
Optional. Public key object.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"EC" Key type indicator.
EC curve name.
EC curve point X. The length of this field must be the full size of a coordinate for the curve specified in the "crv" parameter. For example, if the value of "crv" is "P-521", the decoded argument must be 66 bytes.
EC curve point Y. The length of this field must be the full size of a coordinate for the curve specified in the "crv" parameter. For example, if the value of "crv" is "P-256", the decoded argument must be 32 bytes.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"OKP" Key type indicator.
EdDSA curve name.
EdDSA curve point X. The length of this field must be the full size of a coordinate for the curve specified in the "crv" parameter. For example, if the value of "crv" is "Ed25519", the decoded argument must be 32 bytes.
If the conditions in the "If" tab are respected, then the conditions in the "Then" tab should be respected. Otherwise, the conditions in the "Else" tab should be respected.
"RSA" Key type indicator.
RSA modulus.
RSA exponent.
Key type indicator.