Featured
Posted by
Crista Perlton on May 28th, 2026.
If you’ve used ProGet for a while, you may have heard of pgutil, but maybe never really dug into what it does or why you’d use it. Simply put, pgutil is ProGet’s cross-platform command-line tool for managing your instance without having to do everything through the web UI. It’s especially useful for automating repetitive tasks, scripting...
Featured
Posted by
The Inedo Team on May 22nd, 2026.
ProGet 2026 is now available! This major release introduces the Package Vulnerability Rating System (PVRS); a fundamentally new approach to vulnerability management, helping organizations move beyond theoretical severity scores and focus on what actually matters: whether a vulnerability poses real risk in their environment and what...
Featured
Posted by
The Inedo Team on May 14th, 2026.
Modern software teams are inundated with vulnerability alerts. Although open-source dependencies make up most applications, many organizations still prioritize remediation based on worst-case severity rather than real-world risk. This leading to unnecessary upgrades, avoidable regressions, delayed releases, and wasted effort on...
Featured
Posted by
Eric Seng on April 30th, 2026.
Learn what Source Servers are, what SourceLink is, how they relate to Symbols, and how all three come together to help with NuGet package debugging.
Featured
Posted by
The Inedo Team on April 23rd, 2026.
Modern applications rely heavily on open-source dependencies, which make up most codebases. Organizations rely on tools like repository scanning or automated dependency updating, treating vulnerabilities based on theoretical worst-case severity rather than real-world risk. This can introduce behavior changes that lead to regressions, or...
Featured
Posted by
Crista Perlton on April 16th, 2026.
Having uncontrolled package dependencies can lead to some unintended consequences, like version conflict and even malicious and vulnerable packages. Let’s see what happens when you let those dependency trees go unchecked.
Featured
Posted by
The Inedo Team on March 3rd, 2026.
Back in 2012, a feature flag at Knight Capital accidentally turned on dormant code, triggering uncontrollable trades and a $440 million loss. This kind of failure shows how risky feature flags can be when they’re misused. If teams rely on them to feel safe instead of really understanding the change, even routine deployments can go badly...