> 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/~/revisions/SGhJfnCIOpxRjx1gC1k5/aikido-autofix/autofix-for-open-source-dependencies.md).

# AutoFix for Open Source Dependencies

> Aikido Local Scan accounts DO NOT have access to AutoFix within the UI. In the future, it will be available within our IDE plugins.

Aikido Autofix is a tool you can use to **automatically fix vulnerabilities in open source dependencies** in your projects. It will do this by creating pull requests that remove the vulnerability via package updates or by other means. In some cases an Aikido Autofix can remove a whole class of vulnerabilities instead of just 1 issue..

### Autofix Overview Page <a href="#autofix-overview-page" id="autofix-overview-page"></a>

Aikido allows you to easily create PRs for multiple version upgrades and fixes at the same time. By grouping per repo and lockfile, we ensure that PRs never get to large and are able to be merged without breaking certain parts of the app.

**Important.** By default, Aikido will always give you the minimum version required to do the fix, never a higher one. This means we prioritise minor version bumps always over the major ones, ensuring there are not too many breaking changes on your side. If a major upgrade is proposed, it is because a minor version upgrade would not fix the issue at hand.

![Dependency vulnerability dashboard showing severity, CVEs, version upgrades, and update statuses.](https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-257aba122ae5497e21440e6759611f140460b13f%2Fautofix-for-open-source-dependencies_6b1cd879-9709-4df0-8f9f-23855e0f9d38.png?alt=media)

### Autofix options <a href="#autofix-options" id="autofix-options"></a>

When creating an autofix, multiple options will be presented to you.

* **Upgrade all packages**: upgrades all packages and will contain major, minor and patch upgrades.
* **Minor and Patch Versions Only:** upgrades minor and patch versions only
* **Critical Issues only:** these are the critical issues as defined by Aikido. These can contain major, minor and patch upgrades.

<img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-d47e9205db2acc2609c65aca1a93fd095cc12ab1%2Fautofix-for-open-source-dependencies_3c94580b-c7a2-48cd-a31c-c45b72dcea99.png?alt=media" alt="Options for creating an AutoFix PR to upgrade Python packages in cdk-goat." width="563">

After you will be shown with a progress window (bottom right) on the state of the PR creation. You will receive an update once the PR is ready.

<img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-5451889ccc0b6ad69f33c58288949262f6a77938%2Fautofix-for-open-source-dependencies_16361918-0a43-4db3-b7ff-f250361d5fae.png?alt=media" alt="Aikido initiates an AutoFix pull request to apply code patches." width="375">

### Example of setting up autofix and creating your first PR <a href="#example-of-setting-up-autofix-and-creating-your-first-pr" id="example-of-setting-up-autofix-and-creating-your-first-pr"></a>

[Video](https://ucarecdn.com/4d1a26c8-3ccf-4762-818c-e3430058f9a9/)


---

# 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://help.aikido.dev/~/revisions/SGhJfnCIOpxRjx1gC1k5/aikido-autofix/autofix-for-open-source-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.
