What would happen if someone on your team decided to use a package with a GPL-3 license that requires that the entire code base is open source, under the threat of lawsuits and copyright damages?

Or a package with vulnerabilities, like WinSCPHelper 1.0.13  that allows remote attackers to execute arbitrary programs.

Are you certain that your team hasn’t already?

Dealing with the fallout from security and licensing disasters will make those runtime crashes from NuGet misconfiguration look like a walk in the park.

Open-source NuGet packages on NuGet.org are a part of nearly every single modern .NET application. They’re almost certainly, a part of some of the ones you and your team develop.

Major vulnerabilities, dependencies, and licensing risks are an inherent part of using NuGet. This happens because, while NuGet is easy to get started with, it gets complex quickly. 

Fortunately, not everyone on your team needs to be an expert in all things NuGet. In fact, you don’t even need to be a NuGet expert — just some basic knowledge on how to manage NuGet at scale, as well as the tools and processes to use to make it work.

We’ve updated our free eBook on how to manage your NuGet packages and .NET applications within scaling organizations:

⭐ What exactly is “NuGet”?

⭐ How to Use CI/CD Pipelines for Your NuGet Packages

⭐ Best Practices for Versioning NuGet Packages at Scale

…plus deeper insights to elevate your NuGet strategy.

Check out our updated eBook, NuGet at Scale, which can be read free online, and subscribe to our mailing list for more NuGet tips and tricks: