mcpField
C
cve-research

cve-research

github.com/fusengineSecurity34354 installsUpdated 2w ago
Repository

About cve-research

cve-research is a vulnerability research skill for developers checking a single dependency. It cross-references multiple advisory sources, prioritizes findings by CVSS and exploitability, and reports fixes and workarounds.

Key features

  1. 01Query OSV.dev, NVD, and GitHub Advisory
  2. 02Search recent advisories with Exa
  3. 03Cross-reference vulnerability findings
  4. 04Prioritize by severity and exploitability
  5. 05Report fix versions and workarounds

Use cases

  1. 01Check a dependency for known CVEs
  2. 02Assess vulnerability severity before merging
  3. 03Find recent advisories not yet indexed

Install

Copy the command and run it in a terminal.

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

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

Bundled filesreferences/cve-apis.mdreferences/templates/cve-query.md

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