# Keryn and Endor Labs

> How Keryn compares with Endor Labs, with a source for every row.

Source: https://keryn.dev/compare/endor-labs/

[Endor Labs](https://www.endorlabs.com/) is an application security platform built around dependency reachability.

Every row links the source it comes from ([how these pages are written](https://keryn.dev/compare/)). Vendor statements quote the vendor's own pages as read on 18 November 2026; products change, so follow the link before relying on a row. A missing row is not a claim that the vendor lacks something.

## What they do

| Claim | Source |
|---|---|
| Reachability that traces "exploitability across direct and transitive dependencies down to the specific vulnerable function". | [Endor Labs: reachability](https://www.endorlabs.com/use-case/sca-with-reachability) |
| AI static analysis that "combines pattern matching, dataflow analysis, and multi-pass LLM reasoning". | [Endor Labs: AI SAST](https://www.endorlabs.com/use-case/ai-sast) |
| An inventory of "coding agents, models, MCP servers, skills, and hooks" with policy on agent actions. | [Endor Labs: coding agent governance](https://www.endorlabs.com/use-case/coding-agent-governance) |

## Where they are stronger

| Claim | Source |
|---|---|
| Reachability across many languages and transitive dependencies, packaged for CI. | [Endor Labs: reachability](https://www.endorlabs.com/use-case/sca-with-reachability) |

## Where Keryn differs

| Claim | Source |
|---|---|
| Keryn follows model output into code and tools in the application itself, with a proof level per finding. | [Why the edges](https://keryn.dev/docs/concepts/why-the-edges/) |
| Keryn's rule-based findings are deterministic from the same evidence. | [Scores](https://keryn.dev/docs/concepts/scores/) |

Measured results for Keryn are on the [evaluations](https://keryn.dev/evals/) page, with what each one does not show.
