Skip to content

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

    Security

    View as Markdown

    Report security problems privately to security@keryn.dev. Do not open a public issue. The same address is in /.well-known/security.txt.

    Include the surface or command, a minimal input that triggers the problem, the version (keryn version --json) and what you observed.

    In scope: the CLI, the web app, Keryn Cloud (api.keryn.app, including the demo endpoints), the browser extensions, the editor integrations, the desktop app, the CI adapters, the result, policy and configuration formats, and the rule library. Out of scope: an attacker who already controls the user’s account, and the behaviour of other tools that Keryn’s outputs are fed into.

    We will not argue that a finding is out of scope because the input was malicious. A scanner’s inputs are untrusted by definition.

    Step Target
    Acknowledge the report 3 business days
    Triage and severity 7 business days
    Fix for high severity next patch release, within 30 days
    Fix for medium and low next minor release
    Credit in the release notes, if you want it

    For anything that is not a security report (a question, a bug, a problem with an account), write to support@keryn.dev. This is best effort: we aim to give a first answer within 2 business days, and there is no service-level agreement.

    Every release ships SHA256SUMS, a software bill of materials for Keryn itself, and the licences of everything bundled. Releases are reproducible builds: the same tag gives the same bytes.

    Terminal window
    shasum -a 256 -c SHA256SUMS --ignore-missing