> 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/connect-private-packages/pip-private-packages.md).

# PIP - Private Packages

For Aikido to update dependencies that include private packages, it needs access to your private packages so it can generate accurate requirement file updates. You can provide private git repository configuration in Aikido for this.

## Private PyPI registry <a href="#same-scm-organization" id="same-scm-organization"></a>

You can configure Aikido to authenticate with your private PyPI registry when updating the PIP dependencies by following the steps below:

1. Go to your account's settings page for the autofixer in Aikido, [here](https://app.aikido.dev/issues/fix/settings).
2. Click on "Connect Registry", the private registry modal will now be shown

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-9266e8da54be5ee4e49440d10a643bfa587a37ac%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Select PIP and provide the index URL to the PyPI registry including the username and password in the following format:

```
https://<username>:<password>@domain.com/repo
```

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-49bb08e3ebfb33c6e1d2ba7da696e54740995876%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

4. Click "Connect Registry" to save the configuration.

If the private registry is hosted on **GitHub**, **GitLab**, **BitBucket** or **Azure DevOps**, consult the sections below.

## Private Git repository <a href="#configuration-in-aikido---private-rubygems-repository" id="configuration-in-aikido---private-rubygems-repository"></a>

### Same SCM organization <a href="#same-scm-organization" id="same-scm-organization"></a>

If the private Git repository for the pip is in the same organization as the code being autofixed, make sure your [AutoFix access token](https://app.aikido.dev/issues/fix/settings) has access to the private git repository.

### Different SCM organization <a href="#different-scm-organization" id="different-scm-organization"></a>

You can configure Aikido to authenticate with your private repositories when updating the dependencies by following the steps below:

1. Go to your account's settings page for the autofixer in Aikido, [here](https://app.aikido.dev/settings/integrations/autofix).
2. Click on "Connect Registry", the configuration modal will now be shown

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-9266e8da54be5ee4e49440d10a643bfa587a37ac%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Select "Environment Variables"

<figure><img src="https://3149773201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyKbzcQGrx7UtrG0nPZZ7%2Fuploads%2Fgit-blob-5ef774bba59a2111d8eca7387092882c8f70fff3%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

4. In the example above, we show a possible setup for a private GitHub repository. The environment variable key is `PIP_GITHUB__COM`, and the value is a GitHub access token with repository access.

| Provider     | Environment Variable Key | Value Format        |
| ------------ | ------------------------ | ------------------- |
| GitHub       | `PIP_GITHUB__COM`        | `your-access-token` |
| GitLab       | `PIP_GITLAB__COM`        | `your-access-token` |
| Bitbucket    | `PIP_BITBUCKET__ORG`     | `your-access-token` |
| Azure DevOps | `PIP_DEV__AZURE__COM`    | `your-access-token` |

5. Click "Connect Registry" to save the configuration.


---

# 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/autofix-and-remediation/connect-private-packages/pip-private-packages.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.