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

# Info

The Info tab gives a summary of the project.. The data is presented as widget. The widgets are clickable.

### Component widget

Component widget gives the metadata associated with the project including

* Project Name
* Project Version
* Project created date
* Project created method (scm/image/spdx)
* Depending on the project creation, additional metadata (e.g. source code repo/tag for scm)
* Project owner - user who created the SBOM

### Findings by severity

Findings by severity table summarizes the findings categorized by severity (critical, high, medium, low). Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.

### Vulnerabilities by severity

Vulnerabilities by severity table summarizes the vulnerabilities by severity (critical, high, medium, low). Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.

### Unique components by classification

Unique components table shows the unique components by classification (open source, private, third party, unknown). Unique component number lists down unique components only once. For a project, it is possible that one component may appear at multiple places in the dependency tree (including direct and transitive dependencies). This table de-duplicates the occurrence and gives the unique component count. Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.

### Lineaje Risk Graph

Lineaje Risk Graph shows the overall risk of the project. The graph gives the quadrant where the overall risk of the project falls. The Y axis represents the aggregated Attestation level (LCAL) of all components in the project and X axis represents the aggregated Risk Level (IRL) of all components in the project.

<figure><img src="/files/4a82iNZ7D7V0C6RBMsAR" alt=""><figcaption></figcaption></figure>

### Issue Count by Vulnerability

This chart gives the number of vulnerabilities against open source, private, third party, unknown components grouped by severity (critical, high, medium, low). Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.

### Findings by policy

Findings by policy gives a visualization of the top policies contributing to findings. Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.

### Components by age

Components by age table lists down the number of components that are older than certain age intervals (>36 months, 24-36 months, 18-24 months, 5-18 months). Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.

### Code quality by classification

This chart gives the number of code quality issues against open source, private, third party components grouped by severity (critical, high, medium, low). Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.

### Security posture by classification

This chart gives the number of security posture issues against open source, private, third party components grouped by severity (critical, high, medium, low). Clicking on the numbers will take you to the search page listing down all components belonging to the respective category.


---

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