mcpField
C
cve-research

cve-research

github.com/fusengineSecurity34355 installsUpdated 2w ago
Repository

About cve-research

CVE Research is a skill for checking known vulnerabilities in a single dependency. It is for developers assessing dependency risk and cross-references OSV.dev, NVD, GitHub Advisory, and Exa, then reports prioritization, fix versions, and workarounds.

Key features

  1. 01Queries multiple vulnerability sources
  2. 02Cross-checks reported findings
  3. 03Prioritizes by CVSS and exploitability
  4. 04Reports fix versions and workarounds
  5. 05Limited to one dependency at a time

Use cases

  1. 01Check a dependency for vulnerabilities before merging
  2. 02Prioritize remediation for discovered CVEs
  3. 03Find a dependency's fix version or workaround

MCP support

The skill uses Exa MCP for real-time web search; other vulnerability sources are queried through their respective APIs.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fusengine/claude-plugins --skill cve-research

After installing, type/cve-researchin Claude Code to confirm it loaded.

Details

From the project README
This skill researches known vulnerabilities for a specific dependency across multiple sources: OSV.dev (npm, PyPI, Go, crates, Maven), NVD (CVSS scoring), GitHub Advisory Database (maintainer responses), and Exa web search for advisories not yet indexed.

It queries OSV.dev first for speed and accuracy, cross-checks NVD for CVSS scoring, uses Exa for recent advisories, and checks GitHub Advisory for maintainer responses, then cross-references findings and prioritizes by CVSS score and exploitability — CRITICAL (9.0-10.0) fixed immediately, HIGH (7.0-8.9) before merge, MEDIUM (4.0-6.9) planned, LOW (0.1-3.9) documented — reporting fix versions and workarounds.

Out of scope: this is a single-dependency lookup, not a full project dependency sweep (use dependency-audit for that).

CVE Research Skill

Overview

Research known vulnerabilities for project dependencies using multiple sources.

Data Sources

SourceAPICoverage
NVDnvd.nist.gov/vuln/apiAll CVEs
OSV.devapi.osv.devnpm, PyPI, Go, crates, Maven
GitHub Advisorygithub.com/advisoriesnpm, pip, composer, cargo
Exa SearchVia MCPReal-time web search

Workflow

  1. Extract dependencies from project (package.json, etc.)
  2. Query each source for known CVEs
  3. Cross-reference findings across sources
  4. Prioritize by CVSS score and exploitability
  5. Report with fix versions and workarounds

Query Strategy

For each dependency:

  1. Search OSV.dev first (fastest, most accurate for packages)
  2. Cross-check NVD for CVSS scoring
  3. Use Exa for recent advisories not yet in databases
  4. Check GitHub Advisory for maintainer responses

Severity Mapping

CVSS ScoreSeverityAction
9.0 - 10.0CRITICALFix immediately
7.0 - 8.9HIGHFix before merge
4.0 - 6.9MEDIUMPlan fix
0.1 - 3.9LOWDocument

References

Comments

Markdown supported