> For the complete documentation index, see [llms.txt](https://docs.debricked.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.debricked.com/product/outdated-dependencies.md).

# Outdated dependencies

A dependency can require attention because its version is no longer supported or significantly outdated.

Fortify SCA identifies dependencies that require attention, in addition to security, license, and malware issues. Dependency version status identifies libraries that may need to be updated or replaced.

* **End of life (EOL):** The dependency version is no longer maintained or supported. Upgrade it as soon as possible.
* **Outdated:** The dependency uses an outdated version that may pose a risk. Update to the latest available version when possible.

Review dependencies regularly to reduce exposure to known issues and improve long-term maintainability.

{% hint style="info" %}
Automation rules can notify selected recipients when a dependency is EOL. The notification identifies the affected dependency, its EOL version, and its EOL date.
{% endhint %}


---

# 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.debricked.com/product/outdated-dependencies.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.