dotnet list package vulnerable or NuGet Audit: which should I use?
NuGet Audit warns on every restore, while dotnet list package vulnerable gives an on demand report. Use both, for different jobs. Here is how they differ.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
NuGet Audit warns on every restore, while dotnet list package vulnerable gives an on demand report. Use both, for different jobs. Here is how they differ.
Central package management moves NuGet versions to Directory.Packages.props. Learn what scanners must read, how nested files work and what pinning changes.
.NET 9 is a Standard Term Support release that ends on 10 Nov 2026, the same day as .NET 8. Move to the LTS .NET 10, supported to 14 Nov 2028.
Many open source licenses require notices to ship with the app, so apps commonly include a licenses screen. Android offers a plugin that builds one.
Tree shaking can drop unused exports, but only for ES modules and when side effects allow. It is not a vulnerability fix, so keep upgrading packages.
An IDE plugin only helps if developers keep it on. Ask any vendor about editor support, speed, offline use and whether code leaves the machine.
Before you buy a scanner, ask how it plugs into your CI: native step, CLI, or API. Here are the questions that separate a real fit from a demo-only one.
Scan time decides whether developers accept a gate. Ask about incremental scans, caching and time budgets, then measure on your own repositories.
Monorepos break naive scanners in quiet ways. Ask about project discovery, ownership, scan scope and result grouping before trusting a vendor's claim.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.