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

# Projects

<figure><img src="/files/KsdfPFfE05ZGflEO5Q0P" alt=""><figcaption></figcaption></figure>

Find any connected project, see its security and remediation state, and open its scan history.

The Projects page lists every connected project the factory scans, fixes, verifies, and delivers, with a top-level split between code repositories and container images.

A Vulnerable Projects Summary shows five status cards:

| **Card**                   | **Meaning**                                           |
| -------------------------- | ----------------------------------------------------- |
| In Remediation             | Projects with an active fix running                   |
| Being Verified             | Projects whose fix is in the Verify stage             |
| Needs Review               | Projects with a fix or finding awaiting your approval |
| Scan Errors                | Projects whose last scan failed and need attention    |
| With Novel Vulnerabilities | Projects with at least one open LVE                   |

Use the status filter chips above the project table (All, Delivered, In Progress, Being Verified, With Novel Vulnerabilities) to narrow the list. The table itself shows:

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Column</strong></td><td><strong>Description</strong></td></tr><tr><td>Project</td><td>Project name</td></tr><tr><td>Version</td><td>Project version</td></tr><tr><td>Organization</td><td>Organization the project belongs to</td></tr><tr><td>Type</td><td>Repo or Container</td></tr><tr><td>Last Scan</td><td>Relative time since the last scan, for example 20 minutes ago</td></tr><tr><td>Vulnerabilities</td><td>Open OSS vulnerability counts by severity, shown as C · H · M (Critical · High · Medium)</td></tr><tr><td>Novel Vulnerabilities</td><td>Open LVE counts by severity, shown the same way, plus a Low band</td></tr><tr><td>Status</td><td>Ready for review, Running, FM Scanner is running, In Progress, or Delivered</td></tr></tbody></table>

## Viewing Project Details

{% stepper %}
{% step %}

#### Open a project

Click any project row. A side navigation opens.
{% endstep %}

{% step %}

#### Review the project status

Review the project status bar across Scan, Fix, Verify, and Deliver — a Delivered project shows all four stages complete and confirms every PR has merged.
{% endstep %}

{% step %}

#### Review project details

Review the project details: Project Name, Version, and Last Scanned date.
{% endstep %}

{% step %}

#### Review dependencies and CVE findings

Review dependency counts (Direct Dependencies, Transitive Dependencies) and open exploitable CVE findings.
{% endstep %}

{% step %}

#### Review AI-detected vulnerabilities

Review AI-detected vulnerabilities (LVE), split into Open and Fixed, each broken down by Exploitable, Critical · Non-Exploitable, and High · Non-Exploitable.
{% endstep %}
{% endstepper %}


---

# 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/continuous-vulnerability-elimination-factory-cvef/projects.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.