> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/autofix-and-remediation/scope/autofix-for-open-source-deps-aikido-libraries.md).

# AutoFix for Open Source Dependencies: Aikido Libraries

**Aikido Libraries** gives you access to more than **5,500** patched open-source packages.

Each library is a drop-in replacement for a vulnerable dependency. You keep the same package name, version, and API. You do not need application changes.

When a safe upstream upgrade is blocked by breaking changes, Aikido Libraries lets you stay protected without waiting for a refactor.

## Why teams use it

* More than **5,500** patched libraries are available today.
* Patches target the exact version you already run.
* Every patch is verified by Aikido's security team before release.

## How it works

When a CVE is published, Aikido scans affected package versions, researches the vulnerability, and backports the fix to the exact version you use.

Every patch goes through human verification before release. The result is a patched build of the same package version, with no API changes.

## Example: log4j 1.x

log4j 1.x has been out of maintenance since 2015. Many teams still run it because moving to log4j 2.x is a breaking migration.

Version `1.2.17` contains these critical issues:

* [CVE-2019-17571](https://nvd.nist.gov/vuln/detail/cve-2019-17571) - remote code execution
* [CVE-2020-9493](https://nvd.nist.gov/vuln/detail/cve-2020-9493) - malicious code execution
* [CVE-2022-23305](https://nvd.nist.gov/vuln/detail/cve-2022-23305) - SQL injection

The Aikido Libraries variant of `log4j 1.2.17` fixes these CVEs without forcing a migration to `2.x`.

## Use Aikido Libraries in AutoFix

AutoFix proposes an upgrade to an Aikido Libraries variant when one is available. You can review this in the [AutoFix dependency overview](https://app.aikido.dev/issues/fix). Java variants are hosted on `maven.aikido.io`.

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

To upgrade to the Aikido Libraries variant, select this option in the AutoFix creation modal.

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

## Continuous protection for an entire repository

AutoFix offers Aikido Libraries on a per-CVE basis.

For continuous coverage across a repository, use the **Aikido Libraries** product. It creates daily PRs that pin packages to their Aikido-patched variants, including future CVEs found anywhere in the dependency tree.


---

# 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://help.aikido.dev/autofix-and-remediation/scope/autofix-for-open-source-deps-aikido-libraries.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.