> 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/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="/files/K6BYe3iMW9MkCfAquSM5" 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 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/provenance.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.