dotnet-dependency

Inspect .NET project dependencies using dotnet CLI commands.

137|20|Updated Jun 13, 2025

Search Tags:#security #dependencies #audit #dotnet #nuget #transitive

Ready to run

npx skills add https://github.com/NikiforovAll/claude-code-rules --skill dotnet-dependency

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-dependency
Source: https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-dotnet/skills/dotnet-dependency
Command: npx skills add https://github.com/NikiforovAll/claude-code-rules --skill dotnet-dependency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you understand and manage project dependencies, including why a package is included, listing direct and transitive references, and identifying outdated or vulnerable packages.

Core Features & Use Cases

Dependency reasoning: Use dotnet nuget why to reveal why a package is present in the graph.
Package inventory: List direct and transitive NuGet references with dotnet list package.
Audit & upgrade: Find outdated or vulnerable packages and trace transitive dependencies.

Quick Start

Inspect why a package is included: dotnet nuget why Newtonsoft.Json

Frequently Asked Questions about dotnet-dependency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find out why a NuGet package is included in my .NET project?▼

Use dotnet nuget why to trace why a package appears in your dependency graph. This command reveals the direct or transitive reference path that brought the package into your project, helping you understand unexpected inclusions or verify intentional dependencies.

Can I list all direct and transitive dependencies in my .NET project?▼

Yes, dotnet list package displays all NuGet references in your project. Add --include-transitive to see the complete dependency tree, and use --framework to filter for specific target frameworks if your project supports multiple.

How do I audit my .NET dependencies for vulnerabilities and outdated packages?▼

Run dotnet list package --vulnerable to find security issues and dotnet list package --outdated to identify upgradeable packages. Both commands support JSON output for automation and framework-specific filtering to focus on relevant versions.

What's the best way to trace transitive dependencies across multiple .NET projects?▼

Combine dotnet list package with dotnet list reference to map both NuGet and project dependencies across your solution. Use JSON output to parse and correlate transitive paths, or leverage dotnet-outdated for a consolidated view across projects.

Can I check project references alongside NuGet package dependencies?▼

Yes, dotnet list reference shows all project-to-project references in your solution. Use it alongside dotnet list package to audit your complete dependency structure, including both internal project links and external package inclusions.