cve

Identify CVEs affecting repositories and determine exposure and remediation options.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/yo-go --skill cve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cve
Source: https://github.com/mdmagnuson-creator/yo-go/tree/main/skills/cve
Command: npx skills add https://github.com/mdmagnuson-creator/yo-go --skill cve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security and development teams quickly determine if a CVE affects their systems and what remediation options exist, reducing guesswork during incident response.

Core Features & Use Cases

  • Collect authoritative advisory details from sources like NVD, MITRE, GitHub Advisory Database, and vendor/runtime advisories.
  • Map CVEs to affected components in codebases by scanning dependency manifests (e.g., package.json, go.mod, pyproject.toml), lockfiles, container images, and IaC manifests.
  • Assess exposure and prioritize remediation by evaluating direct vs transitive dependencies, production vs dev paths, and potential exploitation contexts.
  • Propose remediation options with concrete next steps, including version upgrades, mitigations, and rollout considerations.

Quick Start

Run a CVE triage on the target repository to produce a remediation plan.

Frequently Asked Questions about cve

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

FAQPage Schema
How do I check if a CVE affects my repository dependencies?

CVE triage scans dependency manifests, lockfiles, containers, and IaC to map CVEs to affected components and assess exposure. It evaluates direct vs transitive dependencies and production vs dev paths to determine actual risk.

What is the best way to prioritize CVE remediation across multiple repositories?

CVE remediation prioritization applies to single, multiple, or organization-wide scopes by evaluating exposure contexts and exploitation potential. It proposes concrete next steps including version upgrades, mitigations, and rollout considerations.

Which advisory sources are used for CVE risk assessment?

CVE risk assessment collects authoritative advisory details from sources like NVD, MITRE, GitHub Advisory Database, and vendor or runtime advisories to guide software supply chain decisions.

Can I scan lockfiles and container images for vulnerability exposure?

Lockfiles and container images are scanned alongside dependency manifests and IaC manifests to identify vulnerability exposure. This codebase scanning maps CVEs to affected components for accurate remediation planning.

Does CVE triage work for organization-wide software supply chain risk decisions?

CVE triage supports organization-wide scopes to guide risk decisions for software supply chains. It maps CVEs across all repositories to assess exposure and drive remediation with concrete version upgrades and mitigations.

What remediation options are generated after identifying a CVE?

Remediation options include concrete next steps such as version upgrades, mitigations, and rollout considerations. These are determined by evaluating direct vs transitive dependencies and potential exploitation contexts.