> For the complete documentation index, see [llms.txt](https://helm.docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helm.docs.medcrypt.com/ensure-fda-readiness/fda-ready-sbom-and-vulnerability-reports/vex-and-vdr-reports.md).

# VEX and VDR reports

## VEX report

After ingesting your SBOM, Helm will automatically match your components to known software in the NVD and package managers, which will bring forth potential vulnerabilities. Your VEX report contains all of your vulnerabilities that you have added a CycloneDX VEX status to, as well as any rescore information for your vulnerabilities.

### Export your VEX report

1. Click the **Reports** item in the sidebar.&#x20;
2. Click the product version drop-down. You can select one or multiple product versions.
3. In the **Export VEX** report card, click **Export VEX report**. This will export your VEX for all selected products in JSON format.

## VDR report

Our VDR (Vulnerability Disclosure Reports) report offers comprehensive insights into identified vulnerabilities, these reports equip you with proactive mitigation strategies, bolstering your defense against emerging threats. Your VDR report contains all of your  components, as well as all of your vulnerabilities, regardless of their remediation status.

### Export your VDR report

1. Click the **Reports** item in the sidebar.
2. Click the product version drop-down. You can select one or multiple product versions.
3. In the **Export VDR** report card, click **Export VDR report**. This will export your VDR for all selected products in JSON format.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helm.docs.medcrypt.com/ensure-fda-readiness/fda-ready-sbom-and-vulnerability-reports/vex-and-vdr-reports.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
