Endor Labs Dependency Check

Check a specific dependency for known vulnerabilities and malware risks.

Input Parsing

Extract from user input:

1. Package name (required) — e.g., lodash, express, django
2. Version (optional) — e.g., 4.17.15, 2.0.0
3. Language (optional) — auto-detect from package name pattern or manifest files in cwd; ask if ambiguous

Ecosystem Mapping

Workflow

Step 1: Check for Vulnerabilities and Risks

Preferred: Use checkdependencyforrisks MCP tool with ecosystem, dependencyname, and version. This checks for both vulnerabilities AND malware.

Fallback: If checkdependencyforrisks is unavailable, use checkdependencyforvulnerabilities MCP tool (same parameters, vulnerabilities only).

Step 2: Present Results

If Vulnerabilities or Risks Found

## Security Check: {package}@{version}

**Status:** {VULNERABLE / MALWARE DETECTED / VULNERABLE + MALWARE}
**Language:** {language}

### Vulnerabilities Found

| CVE | Severity | Description | Fixed In |
|-----|----------|-------------|----------|
| {cve} | Critical | {desc} | {fixed_version} |

### Malware Risks (if detected)

| Risk | Severity | Description |
|------|----------|-------------|
| {risk_type} | {severity} | {description} |

### Recommended Action

Upgrade to **{safe_version}** to resolve all known vulnerabilities.
If malware detected: **Remove this package immediately** and find a safe alternative.

For install commands, read references/install-commands.md.

### Next Steps

1. `/endor-fix {top-cve}` — Get fix details
2. `/endor-upgrade-impact {package} {safe_version}` — Check upgrade impact

If No Vulnerabilities Found

Report {package}@{version} has no known vulnerabilities in Endor Labs. Suggest /endor-score {package} for package health.

For data source policy, read references/data-sources.md.

Error Handling