NuGet
NuGet License Expressions, Explained
Posted on February 12th, 2026.There are three ways to express a license in a NuGet package: expressions, url, and file. This article is a quick explainer on what NuGet license types are.
There are three ways to express a license in a NuGet package: expressions, url, and file. This article is a quick explainer on what NuGet license types are.
Over the past year or so, the number of malicious packages has grown beyond anyone’s wildest expectations. The rapid, 10,000%+ increase has caused scaling challenges in systems like ProGet, which are designed to detect and block these harmful packages. For ProGet, this translated to timeouts and slowness when processing data...
NuGet Packages are more complex than they appear and have unintended consequences. Read our article to learn how to mitigate them.
How can you balance security checks with your packed schedule? Filter your NuGet packages from the source.
Have you ever noticed how small, everyday issues start piling up while your team is focused on delivering those “big” or “transformative” changes? Hidden dependencies, and operational pressure build into bigger problems: backlogs that never shrink, urgent requests slipping through, and teams constantly putting out fires. What begins as...
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.
If you work with CI/CD pipelines, artifact repositories, or DevOps workflows, you’ll be familiar with Amazon S3. It’s flexible and widely used, but as your repository grows, costs can add up fast. Storage is just one piece of it; request charges and egress fees can catch teams off guard, especially when traffic spikes. As you...
If you’re managing projects that rely on multiple teams delivering consistent components, you’ve probably noticed the chaos that comes from storing build artifacts and libraries in shared folders. Each team has its own way of organizing files, versions get mixed up, and no one really knows which asset the project should be using....
You’re likely pulling OSS packages straight from NuGet.org, npmjs.com, or PyPI.org, via the CLI. It’s the path of least resistance and the fastest way to get what your teams need. But without something sitting in the middle, it’s hard to know exactly what’s being pulled in or whether it meets your org’s requirements. When you pull OSS...