> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-open-source/package-repository-integrations/nexus-repository-manager-connection-setup/nexus-repository-manager-for-npm-1-1.md).

# Nexus repository manager for Go

How to connect Snyk to a Nexus Repository Manager for Go

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Nexus repository manager for Go

{% hint style="info" %}
**Feature availability**

Package repository integrations are available only with Enterprise plans. Visit [pricing plans](https://snyk.io/plans/) for more details.
{% endhint %}

Snyk integrates with Nexus Repository Manager to resolve your private Go modules and transitive dependencies during Open Source (SCA) scans.

You can configure a Nexus Go module proxy from the Snyk web UI, by navigating to **Settings** > **Languages** > **Go**. Use one of two options, depending on how your Nexus instance is reachable. The configuration steps are identical for both options:

* **Private package registries**: Use this option for a publicly reachable Nexus instance protected by credentials. Snyk connects directly. As a prerequisite, ensure to configure your [Nexus integration](/scan-fix-and-prevent/scan-with-snyk/snyk-open-source/package-repository-integrations/nexus-repository-manager-connection-setup.md) first.
* **Brokered package registries**: Use this option for a Nexus instance that is not publicly reachable. As a prerequisite, ensure to configure the [Snyk Universal Broker](https://docs.snyk.io/platform-administration/snyk-broker/universal-broker) first and then enable it for Open Source. For details, visit [Integrate your connection with an Organization that uses Universal Broker](https://docs.snyk.io/platform-administration/snyk-broker/universal-broker/basic-steps-to-install-and-configure-universal-broker).

{% hint style="info" %}
This configuration applies only to Snyk web UI (SCM) integrations. The Snyk CLI automatically uses your private Go proxy from your `GOPROXY` environment and `.netrc` credentials.
{% endhint %}

#### Configure a Nexus Go registry

Ensure you configure a private or brokered package registry integration first. Without it, the following steps do not work, and the registry settings field is not visible on the page.

First, set up the Nexus integration by navigating to **Organization Settings > Add Integration > Nexus > Edit Settings**.

Then, on the **Settings** > **Languages** > **Go** page, complete the following steps:

1. In the **Private package registries** or **Brokered package registries** section, select **Nexus** as the registry type.
2. n the **Registry URL** field, enter the full URL of your Nexus Go (`golang`) proxy repository.
3. Save the integration.

{% hint style="info" %}
Snyk authenticates to the registry with credentials from your Nexus integration. Do not enter credentials here.
{% endhint %}

**Registry URL format**

The URL must point to the Go proxy repository in Nexus. For a Nexus `golang` proxy repository, the URL format is:

```
https://<nexus-host>/repository/<go-repo-name>/
```

Example:

```
https://nexus.example.com/repository/go-proxy/
```

{% hint style="info" %}
Ensure the URL contains no credentials. Provide only the path to the Go repository. Some Nexus copy-URL helpers embed `username:password@` in the host. Remove that portion before you paste the URL. Snyk retrieves credentials from your Nexus integration, not from this field.
{% endhint %}

This is the same base URL you set as `GOPROXY` when fetching modules locally. For example:

```
GOPROXY=https://nexus.example.com/repository/go-proxy/
```


---

# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-open-source/package-repository-integrations/nexus-repository-manager-connection-setup/nexus-repository-manager-for-npm-1-1.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.