# Terms

> Terms of use of Keryn and this site.

Source: https://keryn.dev/terms/

Last updated 2026-11-18.

## Licence

Keryn is proprietary software. Everything Keryn ships (the engine, the CLI, the language server, the extensions, the web
app, the desktop app, the CI integrations, the rule packs, the known-fix database, the policy templates and the schemas)
is licensed under the **Keryn Software Licence**: the file `LICENSE` in every package and at https://keryn.dev/licensing/.

In short, and the licence text governs:

- You may install and run **unmodified** Keryn, obtained from Keryn, to scan code you own or are authorised to scan, for
  your own internal purposes. The output Keryn produces for you is yours.
- You may **not** copy, modify, create derivative works of, redistribute, sublicense, sell, host or offer Keryn as a
  service; decompile, reverse engineer or extract its rules, signatures or database; use it, its rules or its outputs to
  build, train or improve a competing product or a machine-learning model; or remove any notice.
- You **may** measure Keryn's accuracy, coverage and performance for your own internal evaluation. You may **not** publish, or
  disclose to a third party, the results of any benchmark, comparison or performance test of Keryn without Keryn's prior written
  consent (licence section 2).
- The licence is revocable and ends automatically if you breach it.

**Third-party components and vendored rule sets** keep their own licences; their texts and notices ship in `licenses/`, and
those licences govern those components alone. The known-fix database uses data from the CVE Program (cve.org), used under
the CVE Terms of Use, and from the NVD (nvd.nist.gov), a US-government work.

There is no account and no fee for the free surfaces.

## No warranty

The software is provided "as is", without warranties or conditions of any kind, and Keryn is not liable for damages arising
from its use, as far as the law allows. Sections 7 and 8 of the licence have the exact wording.

## What a result means

Keryn's findings, AI-BOMs, policy results and evidence bundles are evidence about your code at the time of the scan: what was found,
where, and how strongly it is supported. They are not a compliance determination and not an audit opinion, and a clean
scan does not show that software is free of vulnerabilities. Decisions based on them are yours.

## Privacy

What Keryn does and does not send is described in `PRIVACY.md`.
