dotnet-library-checker

Validate .NET NuGet dependencies against security policies and approved libraries.

2|Updated Mar 24, 2026

Search Tags:#security #dependencies #compliance #dotnet #upgrade #nuget

Ready to run

npx skills add https://github.com/niltonfrederico/my-agents --skill dotnet-library-checker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-library-checker
Source: https://github.com/niltonfrederico/my-agents/tree/main/skills/dotnet-library-checker
Command: npx skills add https://github.com/niltonfrederico/my-agents --skill dotnet-library-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates .NET dependencies against the juntossomosmais security policies and the approved libraries repository to prevent unapproved or risky packages from entering projects.

Core Features & Use Cases

Dependency Validation: checks NuGet package references against approved lists and company policy rules, including transitive dependencies.
Security & License Analysis: performs vulnerability checks, license compliance validation, and risk assessment.
Upgrade Planning: proposes safe upgrade paths, compatibility guidance, and documentation for approval workflows.

Quick Start

Provide a .NET project path or a list of NuGet packages to validate, and the skill will output a compliance and upgrade plan.

Frequently Asked Questions about dotnet-library-checker

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

FAQPage Schema

How do I validate NuGet packages against security policies in a .NET project?▼

Scan .NET dependencies for vulnerabilities and license compliance by providing a project path or package list. The validation checks transitive dependencies against approved repositories and outputs a structured compliance report with recommended safe upgrade paths.

How does .NET dependency vulnerability scanning work for transitive packages?▼

Vulnerability scanning for transitive packages works by reading .NET project files and checking all referenced NuGet dependencies against company security policies. It identifies hidden risks in transitive packages and generates a compliance report with risk assessments and safe upgrade paths.

Can I check license compliance for NuGet dependencies across multiple .NET projects?▼

Yes, you can check license compliance across .NET projects by validating NuGet package references against company policy rules. The validation reads project configuration files, assesses license risks for direct and transitive dependencies, and produces a structured compliance report for approval workflows.

What is the best way to plan safe upgrades for outdated .NET dependencies?▼

Plan safe upgrades for outdated .NET dependencies by validating them against approved library repositories and security policies. The validation proposes safe upgrade paths, provides compatibility guidance, and documents the necessary steps for approval workflows in a structured report.

Does .NET dependency validation require specific project file formats to work?▼

Dependency validation requires .NET project files to work, specifically reading csproj, packages.config, or nuget.config formats. You provide the project path or a list of NuGet packages, and the validator checks them against approved lists to output a compliance and upgrade plan.