dependency-analyzer

To scan .NET NuGet packages for security vulnerabilities, apply this analyzer to your solution using dotnet CLI commands. It detects CVEs across transitive dependencies, outputs structured reports, and suggests fixes for vulnerable packages.

Finding outdated NuGet dependencies across multiple projects is done by running the analyzer with dotnet list package and dotnet outdated. It reports current versus latest versions per project to streamline maintenance and release planning.

Yes, you can detect version conflicts in transitive NuGet dependencies. The analyzer highlights conflicting package references within your .NET solution and provides specific resolution strategies to fix them.

Yes, the analyzer checks NuGet package licenses for compliance. It reviews licenses across your dependencies to flag potential risks, helping you maintain legal compliance during CI and release planning.

To generate a dependency analysis report for a .NET solution, run the analyzer on your solution via the dotnet CLI. It executes dotnet restore and list commands to output structured reports covering vulnerabilities, outdated versions, and conflicts.

Yes, you can use this NuGet analyzer during CI for maintenance planning. It identifies vulnerable, outdated, or conflicting packages across .NET solutions and projects, providing structured outputs for immediate action.