Product

Overview

How it works Watch it work All 35 features Screenshots How ForgeRepo™ is secured

Keep bad packages out

Malware scanning Typosquat detection Dependency confusion protection Cooling off new releases Allow lists and block lists

When something goes wrong

Kill switch Who has it Lockdown and degraded modes Vulnerability monitoring

Developers and approvals

Requests and auto approve Check, walk and review Waivers Dry run
Formats

Languages

Private npm registry PyPI proxy and private index Private NuGet feed and proxy Maven repository proxy RubyGems mirror Composer and Packagist proxy

Apple, containers and Linux

CocoaPods CDN mirror Swift package registry Docker registry mirror RPM mirror for dnf and yum APT mirror for Debian and Ubuntu

Use it as

An npm firewall Artifacts, SBOMs and lifecycle More than one node SSO, roles and allow lists
Learn

Guides

Learn secure development Secure coding Secure pipelines Unsafe vs safe Security and development

Supply chain

Supply chain attacks, 2016 to 2026 Software supply chain security
Compare Side by side, all four ForgeRepo™ vs JFrog ForgeRepo™ vs Sonatype ForgeRepo™ vs Cloudsmith
Docs

Start

Getting started Download All documentation Questions

For developers

npm setup pip setup docker login Push a Docker image CI basics

For administrators

First setup Rules and their order Six incidents, walked through Backup and upgrade
Pricing Install it
  1. Home
  2. Documentation
  3. Developer Guide
  4. Publish a NuGet package

Publishing

Publish a NuGet package

Push a .nupkg with dotnet nuget push.

The same rules apply as for npm: a publisher role and a reserved package id. Pack the project, then push it with your token as the API key:

Publish a NuGet package
$ dotnet pack -c Release -o nupkgs
  Successfully created package '/work/Acme.Logging/nupkgs/Acme.Logging.1.4.0.nupkg'.
$ dotnet nuget push "nupkgs/*.nupkg" --source https://packages.example.com/nuget/v3/index.json --api-key "$REPO_TOKEN"
Pushing Acme.Logging.1.4.0.nupkg to 'https://packages.example.com/nuget/api/v2/package'...
  PUT https://packages.example.com/nuget/api/v2/package/
warn : Acme.Logging 1.4.0 is pushed. It is listed once its malware scan is clean
  Created https://packages.example.com/nuget/api/v2/package/ 288ms
Your package was pushed.

Captured by running these commands against a real ForgeRepo™.

  • The feed address is the same one you restore from. dotnet finds where to push in it.
  • A pushed version never changes. dotnet nuget delete is refused, so push a new version instead.
  • A new push is held until its malware scan is clean, or until an admin releases it. Then dotnet add package sees it.