> 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/dependencies.md).

# Dependencies

### What are Dependencies?

Dependencies are the components that are required for your application to run.

The dependencies can be open-source, third-party or closed-source(private). Dependencies can be classified as direct and transitive dependencies.

### Understanding Dependencies

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FTSpwIViV7mYV2U72DzXl%2Fimage.png?alt=media&amp;token=1f8e3c7f-fe9c-48f3-b8c2-95a66effdd6d" alt=""><figcaption></figcaption></figure>

* Count of components are displayed towards left, along with the category of the components (open-source, private, third-party, unknown).
* The dependency count is displayed towards the right, giving the number of direct dependencies, number of transitive dependencies, depth of the dependency tree.
* Each tile is clickable which will list down the components applicable to that filter in a table view. The details will list the component name, version, classification and a capsule for dependency counts.
* By clicking the dependency count capsule, next level details are shown as below

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FTswpKopCcUUHN23dL5IW%2Fimage.png?alt=media&amp;token=ca79e0eb-8c64-4f88-add8-72dea1caecb7" alt=""><figcaption></figcaption></figure>


---

# 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/dependencies.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.
