> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/setup-apps-os/artifact-server/configuring-package-managers.md).

# Configuring package managers

Seal serves packages from one host per ecosystem. Each host is public and shared across all Seal customers; the credentials in your package manager configuration are what identify your tenant and your Seal Project. Authentication is HTTP Basic: the [Project ID](/getting-started/creating-a-seal-project.md#project-id-and-project-name) as the username, the [production token](/getting-started/tokens.md) as the password.

| Ecosystem  | Host                                   | Page                                                                                            |
| ---------- | -------------------------------------- | ----------------------------------------------------------------------------------------------- |
| npm        | `https://npm.sealsecurity.io/`         | [Configuring npm](/setup-apps-os/artifact-server/configuring-package-managers/npm.md)           |
| Yarn       | `https://npm.sealsecurity.io/`         | [Configuring Yarn](/setup-apps-os/artifact-server/configuring-package-managers/yarn.md)         |
| pnpm       | `https://npm.sealsecurity.io/`         | [Configuring pnpm](/setup-apps-os/artifact-server/configuring-package-managers/pnpm.md)         |
| Maven      | `https://maven.sealsecurity.io/`       | [Configuring Maven](/setup-apps-os/artifact-server/configuring-package-managers/maven.md)       |
| Gradle     | `https://maven.sealsecurity.io/`       | [Configuring Gradle](/setup-apps-os/artifact-server/configuring-package-managers/gradle.md)     |
| Go modules | `https://go.sealsecurity.io/`          | [Configuring Go](/setup-apps-os/artifact-server/configuring-package-managers/go.md)             |
| pip        | `https://pypi.sealsecurity.io/simple/` | [Configuring pip](/setup-apps-os/artifact-server/configuring-package-managers/pip.md)           |
| Poetry     | `https://pypi.sealsecurity.io/simple/` | [Configuring Poetry](/setup-apps-os/artifact-server/configuring-package-managers/poetry.md)     |
| Bundler    | `https://ruby.sealsecurity.io/`        | [Configuring Bundler](/setup-apps-os/artifact-server/configuring-package-managers/bundler.md)   |
| NuGet      | `https://nuget.sealsecurity.io/`       | [Configuring NuGet](/setup-apps-os/artifact-server/configuring-package-managers/nuget.md)       |
| Composer   | `https://packagist.sealsecurity.io/`   | [Configuring Composer](/setup-apps-os/artifact-server/configuring-package-managers/composer.md) |

The OS-level ecosystems (`rpm.sealsecurity.io`, `deb.sealsecurity.io`, `apk.sealsecurity.io`) are documented under [Seal OS in CI/CD](/setup-apps-os/seal-os-cicd.md).

## Multiple remotes and ordering

Most teams run the Seal Artifact Server alongside one or more other remotes (a private registry for internal packages, sometimes the public registry directly). The order matters because it affects whether Seal sees all pulls or only the sealed ones. See [Artifact server mode](/discovering/package-discovery-mode/artifact-server.md#what-it-sees) for the two configurations and what each one shows in Seal's view.

## Related

* [Editing dependency files manually](/using-platform/working-with-seal-apps/artifact-server.md): pinning sealed versions in the manifest, with direct and transitive override mechanisms.
* [JFrog Artifactory as your remote](/setup-apps-os/artifact-server/jfrog-artifactory.md): integrating Seal as a remote inside an existing JFrog tenant.