endor-scan-full

Build a call graph to identify exploitable vulnerabilities in code.

2|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/endorlabs/skills-ideas --skill endor-scan-full-endorlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: endor-scan-full
Source: https://github.com/endorlabs/skills-ideas/tree/main/skills/endor-scan-full
Command: npx skills add https://github.com/endorlabs/skills-ideas --skill endor-scan-full-endorlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This reachability-enabled security scan identifies which vulnerabilities are actually exploitable by analyzing the full call graph, reducing noise and guiding remediation before release.

Core Features & Use Cases

  • Full reachability analysis with call graph construction to map vulnerability paths from code to potential exploit points.
  • Prioritization of findings by true exploitability rather than severity alone, enabling focused remediation.
  • Pre-release security reviews and ongoing codebase hardening with clear, actionable results.

Quick Start

Run a full reachability security scan on your repository to generate the results in the .endor/scan-full-results.json file.

Frequently Asked Questions about endor-scan-full

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

FAQPage Schema
What is a reachability security scan and how does it find exploitable vulnerabilities?

A reachability security scan builds a full call graph to map vulnerability paths from code to potential exploit points, identifying which vulnerabilities are actually exploitable rather than just listing severity scores.

How do I run a pre-release security scan to gate my software release?

To run a pre-release security scan, execute the Endor MCP workflow to build the call graph and generate reachability findings, caching results to .endor/scan-full-results.json for release gating validation.

Does reachability vulnerability scanning work for large codebases and ongoing hardening?

Reachability vulnerability scanning applies to medium to large projects for ongoing codebase hardening, constructing call graphs to prioritize remediation based on true exploitability across complex code paths.

What is the best way to reduce false positives in vulnerability scanning?

The best way to reduce false positives in vulnerability scanning is using full reachability analysis, which prioritizes findings by true exploitability through call graph construction rather than relying on severity alone.

Do I need the Endor MCP workflow to perform a full call graph security scan?

Yes, you need the Endor MCP workflow with path detection to perform a full call graph security scan, as it builds the reachability analysis and caches detailed findings only after a successful scan.