endor-labs-agent-kit

Triages Endor AI SAST findings using exploit-reproduction evidence, data-flow context, and remediation guidance to distinguish actionable vulnerabilities from noise. It can prepare targeted code fixes and, after explicit approval, edit files and open change requests. For exception workflows, it can create or update scoped Endor exception policies only after verified AppSec approval and explicit user confirmation.

Assesses CI/CD and software supply-chain security across an Endor namespace, GitHub organization, selected repositories, or the current repository. It combines existing Endor SCPM, CI/CD, GitHub Actions, and supply-chain findings with read-only repository configuration evidence and optional local CI inspection to produce deterministic scores, critical overrides, prioritized improvements, and explicit data gaps. It does not modify Endor, GitHub, or repository state.

Compares GitHub repository inventory with Endor projects, GitHub App coverage, monitored branches, scan profiles, package-manager integrations, dependency resolution, and reachability evidence. It identifies onboarding and configuration gaps and provides targeted setup instructions without changing GitHub, Endor, or source repositories.

Evaluates an exact package version, summarizes package risk, or reviews dependencies declared by a repository through one focused workflow. It uses available vulnerability, malware, package-health, license, policy, and Endor evidence to provide a read-only recommendation and clearly identify missing information.

Use when setting up Endor Labs Agent Kit for VS Code / Copilot, checking readiness, verifying Endor auth, choosing namespaces, or diagnosing missing endorctl, gh, Copilot agent plugins, Endor MCP, or workflow prerequisites.

Browses, filters, and summarizes existing Endor findings without starting new scans or performing remediation. It shows the applied scope and filters, relevant severity and reachability context, pagination or truncation limits, and any evidence gaps affecting the results.

Correlates current software supply-chain malware intelligence for affected packages and versions with Endor inventory across a namespace and its child namespaces. It distinguishes confirmed exposure, possible exposure, not-observed exposure, and insufficient data using exact package, version, and inventory evidence. It reports affected projects, indicators of compromise, containment guidance, and recommended follow-up actions without modifying Endor or source systems.

Evaluates candidate dependency upgrades using Endor VersionUpgrade data, Code Impact Analysis, findings, breaking-change information, and Endor-provided manifest targets. It compares findings fixed or introduced and explains the safest available upgrade path, including whether to upgrade now, proceed cautiously, defer, or gather more evidence.

Previews safe remediation options for existing Endor findings without changing code or opening a pull request. It compares VersionUpgrade and Upgrade Impact Analysis candidates using findings fixed, upgrade risk, compatibility evidence, and available data, then recommends the safest evidence-backed next step.

Plans and applies dependency-vulnerability fixes using Endor SCA findings, VersionUpgrade and Upgrade Impact Analysis evidence, deterministic risk decisions, and local validation. It separates low-risk changes from upgrades requiring deeper compatibility review and requires explicit approval before editing files, pushing branches, opening change requests, or creating tickets.

Diagnoses Endor setup, authentication, integration, scanning, dependency-resolution, container, reachability, policy, and workflow problems. It gathers the smallest useful set of read-only evidence needed to identify the likely root cause and recommend the lowest-friction repair without modifying Endor, source-provider, or repository state.

Explains a CVE, GHSA, or Endor vulnerability, optionally in the context of a supplied package and version. It summarizes severity, exploitability signals, affected and fixed versions, recommended remediation, and relevant reachability or repository context when supported by exact Endor evidence. It clearly identifies missing information rather than inferring package or project applicability.