NuGet
How to Filter Unwanted Packages from NuGet.org
Posted on January 22nd, 2026.How can you balance security checks with your packed schedule? Filter your NuGet packages from the source.
How can you balance security checks with your packed schedule? Filter your NuGet packages from the source.
CI/CD for NuGet packages isn’t just a pain – it sometimes feels downright impossible.
Versioning seems so simple – it’s just a number! But with NuGet, it’s anything but that. There are five distinct, multi-part version numbers that can be in a package, and each of these has its own formatting rules and behaviors.
Software Bills of Materials (SBOMs) are becoming something every developer needs to deal with. If your organization uses NuGet packages you’ve probably heard of them, but finding guidance that actually applies to NuGet can be a bit of a pain, since most resources focus on other ecosystems like npm or Maven. For many teams,...
Include NuGet Packages into your company's pre-existing third-party software policy to check the license type and avoid potential lawsuits.
This article is part of our series on NuGet at Scale, also available as a chapter in our free, downloadable eBook Using NuGet in your development starts out easy, a few projects, a small team, grabbing packages from NuGet.org. But as your org grows, things slowly get messy. More teams, more repos, more tools, all adding to the chaos....
NuGet is the go-to package manager for .NET and is built right into tools like Visual Studio, making adding, updating, and managing libraries super easy. By default, Visual Studio pulls packages from NuGet.org—but giving your team unrestricted access to all those packages can be risky. Over 80% of projects rely on outdated dependencies,...
Learn about the complexities of NuGet, the risks of using third-party packages from NuGet.org, and how to effectively manage both proprietary and open-source packages in the enterprise.
When you develop .NET applications, you most certainly will work with NuGet packages to manage libraries and dependencies. Making sure these packages are safe for production use is a crucial responsibility. Chances are you've also used the NuGet or dotnet CLI to scan all your packages.
Debugging your NuGet packages can be a total pain. In fact, it’s one of the main reasons that development teams are hesitant to break apart their monolithic .NET solution. Fortunately, there's a pretty easy solution to this problem; NuGet Symbol Packages. In this article I’ll discuss how.