Run any Skill in Manus with one click

nuget-audit

Stars2

Forks0

UpdatedJuly 9, 2026 at 11:54

Audit NuGet dependencies for vulnerabilities, deprecated packages, and outdated versions across the solution. Use when the user asks about package health, security vulnerabilities in dependencies, or updating packages.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

cwoodruff

cwoodruff/dotnet-claude-code-kit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	nuget-audit
description	Audit NuGet dependencies for vulnerabilities, deprecated packages, and outdated versions across the solution. Use when the user asks about package health, security vulnerabilities in dependencies, or updating packages.
allowed-tools	Bash(dotnet list ), Bash(dotnet restore), Bash(dotnet add ), Bash(dotnet build), Read, Grep, Glob

NuGet Dependency Audit

Restore first so metadata is current: dotnet restore
Gather three views of the solution:
- dotnet list package --vulnerable --include-transitive
- dotnet list package --deprecated
- dotnet list package --outdated
Produce a report table: Package | Current | Status (vulnerable/deprecated/outdated) | Severity/Advisory | Recommended version | Breaking-change risk.
Prioritize: vulnerabilities (by severity) → deprecated → major-version-behind → minor/patch.
For each vulnerable package, state whether the vulnerable code path is plausibly reachable from this codebase (grep for usage) — don't just list CVEs.
Propose an upgrade plan in safe batches (patch/minor first). Only run dotnet add package upgrades the user approves, one batch at a time, building and running tests between batches.
Flag transitive-only vulnerabilities separately and recommend either a direct pin or upstream bump.

More from this repository

same repository

add-endpoint

cwoodruff/dotnet-claude-code-kit

Add a new Minimal API endpoint following this solution's conventions. Use when the user asks to add a route, endpoint, or new API operation (GET/POST/PUT/DELETE).

2026-07-092

async-hygiene

cwoodruff/dotnet-claude-code-kit

Find and fix async/await anti-patterns in C# code — blocking calls, async void, missing cancellation, fire-and-forget. Use when reviewing async code, diagnosing deadlocks or thread-pool starvation, or when the user asks about async correctness.

2026-07-092

dotnet-upgrade

cwoodruff/dotnet-claude-code-kit

Plan and execute an upgrade of a project or solution to a newer .NET version (e.g. .NET 8 to .NET 10). Use when the user asks to upgrade, migrate, or modernize the target framework.

2026-07-092

ef-migration

cwoodruff/dotnet-claude-code-kit

Create, review, and apply an EF Core migration safely. Use when the user wants to add a migration, change the database schema, add/modify entity properties, or asks about database changes.

2026-07-092

gen-tests

cwoodruff/dotnet-claude-code-kit

Generate an xUnit test suite for a class, endpoint, or file. Use when the user asks for tests, test coverage, or to test something they just wrote.

2026-07-092

summarize-changes

cwoodruff/dotnet-claude-code-kit

Summarize uncommitted changes and flag risks. Use when the user asks what changed, wants a commit message, or asks to review their diff.

2026-07-092

name	nuget-audit
description	Audit NuGet dependencies for vulnerabilities, deprecated packages, and outdated versions across the solution. Use when the user asks about package health, security vulnerabilities in dependencies, or updating packages.
allowed-tools	Bash(dotnet list ), Bash(dotnet restore), Bash(dotnet add ), Bash(dotnet build), Read, Grep, Glob

NuGet Dependency Audit

Restore first so metadata is current: dotnet restore
Gather three views of the solution:
- dotnet list package --vulnerable --include-transitive
- dotnet list package --deprecated
- dotnet list package --outdated
Produce a report table: Package | Current | Status (vulnerable/deprecated/outdated) | Severity/Advisory | Recommended version | Breaking-change risk.
Prioritize: vulnerabilities (by severity) → deprecated → major-version-behind → minor/patch.
For each vulnerable package, state whether the vulnerable code path is plausibly reachable from this codebase (grep for usage) — don't just list CVEs.
Propose an upgrade plan in safe batches (patch/minor first). Only run dotnet add package upgrades the user approves, one batch at a time, building and running tests between batches.
Flag transitive-only vulnerabilities separately and recommend either a direct pin or upstream bump.