> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/product/exporting-sbom/sbom-export/cyclonedx-sbom-export.md).
# CycloneDX SBOM export
Learn how to create a CycloneDX SBOM Export.
{% hint style="info" %}
*This feature is only available for* [*SCA Enterprise*](https://debricked.com/pricing/) *users. Already have an account?* [*Click here to upgrade.*](https://debricked.com/app/en/repositories?billingModal=enterprise,free)
{% endhint %}
### **What is CycloneDX?**
CycloneDX, developed by the Open Web Application Security Project (OWASP), is an open common standard for communicating SBOM information, a data format.
#### Dependency relations
In the dependencies array, you can find a reference number (ref) for each component and an array of each direct dependency of that dependency (depends\_on). The roots of the relational trees will reference to the files in the project, together with the direct dependencies that it contains. By traversing the dependencies array, it is possible to build the entire dependency tree.
In example below, you can see the direct dependency *\`webpack:4.28.4\`* depending on *\`terser-webpack-plugin:1.2.1\`* which in turn depends on *\`terser:3.14.1\`.*
```
"dependencies": [
{
"ref": "e771afadf654cc12c324a0dd716518dd",
"depends_on": ["cpe:2.3::~:webpack:4.28.4:~:~:~:~:~:~:~"]
},
{
"ref": "cpe:2.3::~:webpack:4.28.4:~:~:~:~:~:~:~",
"depends_on": ["cpe:2.3::~:terser-webpack-plugin:1.2.1:~:~:~:~:~:~:~"]
},
{
"ref": "cpe:2.3::~:terser-webpack-plugin:1.2.1:~:~:~:~:~:~:~",
"depends_on": ["cpe:2.3::~:terser:3.14.1:~:~:~:~:~:~:~"]
},
{
"ref": "cpe:2.3::~:terser:3.14.1:~:~:~:~:~:~:~",
"depends_on": []
}
]
```
Here is how this would be visualised in the user interface:
#### Root fixes
Under **Recommendation,** you can find information about the first version of the specific vulnerable dependency that is safe, as well as the first version of the root or direct dependency that does not contain a vulnerable version of the indirect dependency. See example below:
```
"recommendation": "Multiple components are affected by this vulnerability.
Component: pkg:npm/async@3.2.0
Safe version: 3.2.2.
Root fixes: Update root dependency pkg:npm/htmlhint@0.14.2 to 0.16.2.
---------
Component: pkg:npm/async@2.6.0
Safe version: 2.6.4.
Root fixes: Update root dependency pkg:npm/gelf-pro@1.2.2 to 1.3.4.",
"created": "2022-04-06T17:15:00+00:00",
"published": "2022-04-06T17:15:00+00:00",
"updated": "2022-04-06T17:15:00+00:00",
"affects": [
{
"ref": "pkg:npm/async@3.2.0"
},
{
"ref": "pkg:npm/async@2.6.0"
}
],
"references": [
{
"id": "GHSA-fwr7-v2mv-hh25",
"source": {
"url": "https://github.com/advisories/GHSA-fwr7-v2mv-hh25",
"name": "GitHub"
}
}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.debricked.com/product/exporting-sbom/sbom-export/cyclonedx-sbom-export.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
