Skip to content

    Type a page, a command such as keryn scan, or a rule id.

    Other scan providers

    View as Markdown

    Add the decision and evidence layer above your findings. Keryn is pre-release; every partnership starts as a time-boxed pilot.

    Every scanner produces findings. Buyers still ask which matter, whether they are reachable, and what the evidence is. They also ask for AI and agent coverage that most scanners lack.

    • A decision and evidence layer over your output: import SARIF and get a proof level, location, coverage statement and recorded decision per finding.
    • An engine or feed beside yours: rule metadata (id, severity, languages, taxonomy, remediation) is public. Rule logic stays with Keryn.
    • Neutral measurement: the eval method runs any engine’s output against labelled corpora and reports numerators, denominators and limitations. Keryn publishes its own, including gaps.
    Scan provider integration A scan provider exchanges SARIF with Keryn in both directions and can compare engines on a shared labelled corpus using the published eval method. Keryn adds decisions and coverage statements; its rule metadata is public. Partner environment Integration surface Keryn Provider scannerSAST, DAST, SCA or AI Provider product / APIshows findings SARIF in and outrule ids, locations kept CLI --json in CIexit codes Eval harnessshared corpus, numerators and denominators Decision + evidence layerproof level, coverage, decisions Rule metadataid, severity, taxonomy (public) keryn.dev/evalspublished results incl. gaps findings feed with consent solid: real dashed: partial dotted: roadmap
    • SARIF in and out, CycloneDX for AI-BOM.
    • The CLI in your CI with JSON output and exit codes.
    • The hosted customer API for batch work.
    • A shared-corpus comparison under the published eval method, published only with your consent.
    Surface Status
    SARIF in and out Available
    Rule metadata catalogue Public at keryn.dev/rules
    Eval comparisons Method public; joint runs on request
    Embedded engine or licensed feed Sales-led; contract-versioned engine, no packaged library yet
    @keryn/sdk TypeScript client See Download for npm availability

    See deployment models for who operates what.

    • Parity: on a public corpus Keryn’s findings agree with the reference engine (Semgrep CE 1.157.0) on 10,306 of 10,306 findings, with one extra (receipt 2026-11-02).
    • Detection: recall is 0.34 on 582 real-fix pairs, published with its denominator and its gaps (scoreboard 2026-10-28).
    • Known fixes: 3,156 signatures in the known-fix database (2026-10-28).
    • Local first: the CI copy-paste run made no network attempts (2026-11-02).
    • Every evaluation suite, with inputs, denominators and limits, is at keryn.dev/evals.

    Evaluation is free. If you call the API, credits at a partner rate (10 to 30 percent off list by annual commit). A feed or engine licence is an OEM agreement: a platform licence from $40,000 per year per field of use. See partner terms. Contracts are drafted per partner and reviewed by counsel before signature.

    Days Keryn You
    1-5 Mutual NDA; agree what may be published Name an engineer and a product owner
    6-12 Round trip on a public repository: their SARIF in, ours out Provide a sample findings file and their ingestion contract
    13-20 Shared-corpus comparison, internal only Review disagreements case by case
    21-27 Decide: feed, co-published eval, or stop Same
    28-30 Written summary with evidence states Same

    Exit criteria: Round trip loses no finding and no location; disagreements are explained, not hidden; publication terms agreed before any number leaves the building.

    One sanitised sample of your findings, or one operation of your ingestion contract.

    Become a partner or write to keryn@keryn.dev.