> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/projects/suppliers-and-licenses.md).

# Suppliers & Licenses

SBOM360 analyses the software suppliers, licenses, and presents them all within your SBOM project at both the SBOM and component level. To ensure supply chain security, it is important for you to carefully vet your suppliers and conduct thorough security assessments of the software they provide. Licensing information can helps ensure that the software is compliant with open-source, private, and third-party licensing requirements.

### Understanding Suppliers & Licenses

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FGTdg4k5kt8Ykvz0zDWNq%2Fimage.png?alt=media&amp;token=2d62bdc9-c95f-47ee-ae55-77547b8998f2" alt=""><figcaption></figcaption></figure>

Total Suppliers: List all suppliers in the current SBOM. This gives the metadata for the supplier like Name, Organization, Website, number of components by this supplier in this SBOM, number of components by this supplier across all your SBOMs in your organization.

Total Project Licenses: List unique license category and license name. This gives the metadata like license category, license name, license version, license URL.

Total unique Authors: List the authors responsible for code commits. This gives the metadata like contributor name, email, number of commits.

Total Supplier Components: All components in the current project that are contributed by the suppliers.

<br>

<br>


---

# 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.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/projects/suppliers-and-licenses.md?ask=<question>&goal=<user_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.
