> 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/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
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.
---
# 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://docs.veedna.com/sbom360/projects/suppliers-and-licenses.md?ask=&goal=
```
`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.