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

# Provenance

### What is Provenance?

Provenance refers to the author, region of commits on your source code.

It illustrates the history of your code so you can better understand the origins and trustworthiness of the software.

### Understanding Provenance

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2F8wCddyPHyQU3qXeZ4hxP%2Fimage.png?alt=media&amp;token=b2540fc1-42e4-4df4-ac23-e70b4fd199f3" alt=""><figcaption></figcaption></figure>

* Count of components that are with provenance information is displayed towards left, along with the category of the components (open-source, private, third-party, unknown).
* The top countries contributing to the code commits is displayed in the middle
* The top authors contributing code is listed towards the right.
* 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, supplier, a capsule for contributors and a capsule for countries.
* By clicking the capsule, next level details will be shown.
* By clicking on any row, the sidesheet shows up.

<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/provenance.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.
