Quick Start: NuGet

Get your first NuGet package published and consumed through DepAegis in under five minutes. This guide walks you through creating a class library, packing it, pushing it to your private registry, and installing it in another project.

Prerequisites

• .NET SDK 8 or later — verify with dotnet --version
• A DepAegis account with access to an organization — sign up free at app.depaegis.com
• A terminal or command prompt

Step 1 — Create an access token

DepAegis authenticates NuGet operations using Personal Access Tokens (PATs). Create one from the DepAegis dashboard:

1. Navigate to Settings → Access Tokens
2. Click Generate new token
3. Give it a descriptive name (e.g. nuget-cli)
4. Select the write:packages scope if you plan to publish
5. Copy the token value — you will not be able to see it again

Step 2 — Configure the NuGet source

Register DepAegis as a NuGet package source. The NuGet endpoint is https://app.depaegis.com/api/v1/nuget/v3/index.json.

Option A: .NET CLI

dotnet nuget add source "https://app.depaegis.com/api/v1/nuget/v3/index.json" \
  --name depaegis \
  --username "<your-username>" \
  --password "<your-access-token>" \
  --store-password-in-clear-text

Option B: nuget.config file

Alternatively, place a nuget.config file in your project or repository root:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="depaegis"
         value="https://app.depaegis.com/api/v1/nuget/v3/index.json" />
  </packageSources>
  <packageSourceCredentials>
    <depaegis>
      <add key="Username" value="<your-username>" />
      <add key="ClearTextPassword" value="<your-access-token>" />
    </depaegis>
  </packageSourceCredentials>
</configuration>

Step 3 — Create a class library

Create a new class library project that will become your NuGet package:

mkdir MyCompany.Utils && cd MyCompany.Utils
dotnet new classlib -n MyCompany.Utils

Add some code to the default class file. For example, open Class1.cs and replace its contents:

namespace MyCompany.Utils;

public static class StringExtensions
{
    public static bool IsNullOrEmpty(this string? value)
        => string.IsNullOrEmpty(value);
}

Step 4 — Pack the package

Build and pack the library into a .nupkg file:

dotnet pack -c Release

The resulting package will be in bin/Release/MyCompany.Utils.1.0.0.nupkg. You can customize the version, description, and other metadata in the .csproj file:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <PackageId>MyCompany.Utils</PackageId>
    <Version>1.0.0</Version>
    <Authors>Your Name</Authors>
    <Description>Shared utility extensions for MyCompany projects.</Description>
    <PackageLicenseExpression>MIT</PackageLicenseExpression>
  </PropertyGroup>
</Project>

Step 5 — Push to DepAegis

Publish the package to your DepAegis registry:

dotnet nuget push "bin/Release/MyCompany.Utils.1.0.0.nupkg" \
  --source depaegis

If you did not name your source depaegis, use the full URL instead:

dotnet nuget push "bin/Release/MyCompany.Utils.1.0.0.nupkg" \
  --source "https://app.depaegis.com/api/v1/nuget/v3/index.json" \
  --api-key "<your-access-token>"

Step 6 — Consume the package

In another project, install the package from DepAegis:

dotnet add package MyCompany.Utils --source depaegis

Or add it directly to your .csproj file:

<ItemGroup>
  <PackageReference Include="MyCompany.Utils" Version="1.0.0" />
</ItemGroup>

Then restore and use it:

dotnet restore --source depaegis

using MyCompany.Utils;

var input = Console.ReadLine();
if (input.IsNullOrEmpty())
{
    Console.WriteLine("No input provided.");
}

Step 7 — Verify the security scan

Open the DepAegis dashboard and navigate to the package page for MyCompany.Utils. You will see:

• Vulnerability scan results — any CVEs detected in the package or its dependencies, rated by severity
• SBOM — the full Software Bill of Materials in CycloneDX format
• Activity log — a timestamped record of the push operation

Next steps

• Configuring NuGet — advanced source configuration and Visual Studio integration
• Publishing NuGet Packages — versioning and CI/CD pipelines
• Vulnerability Scanning — how DepAegis scans packages and reports findings
• GitHub Actions Integration — automate publishing from your CI/CD pipeline