How to Approve and Promote Open-source Packages in ProGet

In ProGet, package promotion is simply a process of copying a package from one feed into another, and keeping a record of that promotion. This is a reliable way to ensure that only approved and verified packages are used in the right environments.

This article will walk you through a common scenario of promoting open-source NuGet packages. We'll use NuGet packages from NuGet.org, along with an unapproved-nuget and approved-nuget feed, but these steps can apply to any type of package.

Step 1: Create new feeds

The first thing we'll be doing is creating two "NuGet" feeds, one for unapproved packages, and the other for approved packages that have been promoted.

We start by selecting "Feed" and [Create New Feed].

As we will be using packages from Nuget.org, we select "NuGet (.NET) Packages".

Step 2: Configure feeds

After selecting the feed type, we’ll specify that the feed will connect directly to "NuGet.org".

We will then select "Yes, Create Two Feeds", as for a package to be promoted from one feed to another, there must be multiple feeds.

In this example, we will create an unapproved-nuget feed where unverified packages from "NuGet.org" will be stored, and an approved-nuget feed for our packages to be promoted to.

Step 3: Naming feeds

We then name our feeds as we specified above, and then click [Create Feeds].

We are then presented with several options. More information on these can be found in the Vulnerability Scanning and Blocking and SCA and Continuous Integration (CI) documentation.

Finally, we select [Set Feed Features], which will create the feeds and redirect us to our unapproved-nuget feed, populated with packages from "NuGet.org".

Step 4: Set Permissions

There are many ways to configure security access controls for uses and groups in ProGet. For this example, we want to permit only senior developers to promote packages to approved-nuget feed since they're trained to verify the quality, licenses, and vulnerabilities of open-source packages. To ensure this rule, we'll set up a new permission. By default, only administrators have assigned permissions.

To start, we navigate to "Settings" > "Manage Security".

We then navigate to the "Tasks / Permissions" tab, listing the currently configured permissions, and select "add permission".

Next, we will fill out the following dialog to give the "Senior Developers" user group permission to "Promote Packages" from the unapproved-nuget feed.

Following the same steps, we will also give the "Developers" user group permission to "View and Download" packages from the approved-nuget feed.

After saving these two privileges, our task overview page looks like this:

How to Promote Packages

Promoting packages implies that someone approves a package, often after following an internal process that involves checking the license, vulnerabilities, and quality.

ProGet's integrated license and vulnerability scanning can help by automating the scanning and verification, but there's usually human judgment involved.

Example: Newtonsoft.Json

Most organizations would find the Newtonsoft.Json NuGet package to be acceptable in terms of license, vulnerabilities, and quality. This guide will demonstrate how we would promote this package.

We start by clicking the "version number" (in this case 13.0.3) to direct us to the package page, and then simply select "Promote Package" from the drop-down menu on the right side.

From here, we fill out the dialog box with any comments, and finally select [Promote]:

Since we configured a package approval workflow earlier, this package can only be promoted to the approved-nuget feed. Without that configured, there would be a choice of feeds to promote to.

After clicking promote, the package will now be available in the approved-nuget feed for all "Developers" to view and download.

Package promotion can also be done using the Package Promotion API. The API usage is limited to paid users, however.

Viewing Promotion History

ProGet keeps a package history that outlines what actions were taken by whom. For example, to view the history of the "Newtonsoft.Json" package, we navigate to the package page and click the "History" tab.

The history tracks over both feeds, and shows us that we promoted this package from unapproved-nuget to approved-nuget.

Advanced: Repackaging

Package promotion can also be used with prerelease packages and repackaging. This is best for packages developed in-house, and is done by creating a CI package, repackaging it to an RC package, and then repackaging and promoting it once more to a stable package in a different feed.