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

# Components

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

Review the AI-recommended fix plan for each vulnerable component. Plans include a recommended version, estimated effort, and plan type.

**Components** displays AI-recommended fix plans across all projects. Each plan explains how CVEF will remove a component vulnerability.

| **Card**        | **Meaning**                                               |
| --------------- | --------------------------------------------------------- |
| Total           | Components with a fix plan                                |
| Available       | Fixes ready to apply. A Gold OSS alternative is available |
| Premium Pending | Premium fixes still in development                        |
| Awaiting Action | Fixes awaiting pull request (PR) approval                 |

Use the following columns to identify affected components and assess their recommended fixes.

<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 / Project Version</td><td>Project name and version</td></tr><tr><td>Component Name</td><td>Package name, such as npm:forever:2.0.0</td></tr><tr><td>Version</td><td>Current vulnerable version</td></tr><tr><td>Fix Version</td><td>Recommended fix version, such as 2.3.2-lineaje-01</td></tr><tr><td>Efforts</td><td>Estimated remediation effort: low, medium, or high</td></tr><tr><td>Plan Type</td><td>Rebuild, Curated, or Premium</td></tr></tbody></table>


---

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