security-cve-review

Inventory NuGet and container dependencies, query OSV.dev, and assess CVE reachability.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill security-cve-review-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-cve-review
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/security-cve-review
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill security-cve-review-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually tracking vulnerabilities across NuGet packages and Aspire-managed container components is slow and error-prone, and raw scanner output rarely tells you whether a CVE is actually reachable in your code. This Skill automates the full dependency CVE review and adds a reachability judgment for each match. ## Core Features & Use Cases - Dependency Inventory: Enumerates NuGet packages and Aspire-managed container/infrastructure components, flagging which ones ship in the runtime versus build-only tooling. - OSV.dev Cross-Reference: Queries the OSV.dev API for known vulnerabilities matching each inventoried component and version. - Reachability Assessment: Analyzes how the application actually uses each vulnerable dependency and classifies findings as reachable, not-reachable, or unknown. - Persistent Findings & Reports: Stores findings in a structured findings store, auto-resolves findings when packages are patched, and renders a dated snapshot plus a cross-capability report. - Use Case: Before a release, run a full dependency review to get a report showing every CVE match with severity and reachability, so the team patches only what actually matters first. ## Quick Start Ask the assistant to run a dependency CVE review of this repository against OSV.dev and show the findings with reachability.

Frequently Asked Questions about security-cve-review

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

FAQPage Schema
How do I check .NET NuGet dependencies for known vulnerabilities?▼

Run the dependency CVE review, which inventories all NuGet packages and Aspire-managed container components, then queries the OSV.dev API for matching vulnerabilities. Results are stored as findings with severity and reachability labels.

How to tell if a CVE is actually exploitable in my application?▼

The review assesses reachability by reading the OSV advisory and cross-referencing how the dependency's APIs are actually called in the projects that use it. Each finding is labeled reachable, not-reachable, or unknown rather than presented as a raw list.

Does the OSV.dev scan work for container and infrastructure components?▼

Yes, the inventory step covers Aspire-managed container and infrastructure components in addition to NuGet packages, and all of them are cross-referenced against OSV.dev. Components that do not ship in the runtime are still reported but flagged as lower relevance.

What happens if OSV.dev is unreachable during a vulnerability scan?▼

The review stops and reports the error to the user instead of persisting a partial or empty result. This prevents a failed query from being recorded as a clean review with zero findings.

Do resolved vulnerabilities disappear after upgrading a package?▼

Yes, because every run covers the full dependency set, a component upgraded to a patched version automatically resolves its prior finding in the findings store. The dated snapshot file preserves the point-in-time state for that day.