> 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/nuget.md).

# Configuring NuGet

NuGet configures package sources through `NuGet.config` files. The Seal Artifact Server is registered as a package source, with credentials supplied either in `NuGet.config` directly or through a credential provider.

## Configuration

Create or edit `NuGet.config` in the project root (or the solution root):

```xml
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="seal" value="https://nuget.sealsecurity.io/v3/index.json" />
  </packageSources>
  <packageSourceCredentials>
    <seal>
      <add key="Username" value="<project-id>" />
      <add key="ClearTextPassword" value="<token>" />
    </seal>
  </packageSourceCredentials>
</configuration>
```

Replace `<project-id>` with the Seal [Project ID](/getting-started/creating-a-seal-project.md#project-id-and-project-name) and `<token>` with your production token.

`ClearTextPassword` stores the token literally; for CI, prefer passing credentials at runtime through `nuget sources update` or an environment-based credential provider rather than committing them.

## Verify

```bash
dotnet nuget list source
```

The output should include `seal` pointing at `https://nuget.sealsecurity.io/`. A clean `dotnet restore` should then resolve packages from that source.

## Related

* [Editing dependency files manually](/using-platform/working-with-seal-apps/artifact-server/nuget.md): pinning sealed versions in `*.csproj`.