Skip to main content

NuGet - Package Source Mappings

With NuGet 6.0, a new feature Package Source Mapping was introduced. Goal of this feature is to help improve security by safeguarding your software supply chain.

What is Package Source Mapping?

If I want to explain what Package Source Mapping is, I should start by explaining the concept of a Package Source. In NuGet a Package Source is the source where nuget searches for packages. This can a public source(like nuget.org) and/or a private source(like Azure Artifacts or a local disk).

You can add a package source by executing the following command:

dotnet nuget add source <source> –n MySource

It is possible to define multiple sources. By default when multiple sources are defined nuget will scan all configured package sources to find and restore a specific package. This introduces a risk as you are not sure where a specific package is coming from.

A risk that can be mitigated by using Package Source Mapping(PCM). PCM allows to centrally declare which source each package in your solution should restore from in your nuget.config file.

You can configure Package Source Mapping directly in the Visual Studio IDE.  For each mapping you need to specify a pattern and one or more package sources:


This will update your nuget.config file like this:

Starting from NuGet 6.7 this got improved even further as you can easily see when NuGet packages are (not) mapped to respective package source(s):


More information:

Announcing NuGet 6.7 – Keeping You Secure - The NuGet Blog (microsoft.com)

Package Source Mapping | Microsoft Learn

dotnet nuget add source command - .NET CLI | Microsoft Learn

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more