Security
Reporting a vulnerability
Section titled “Reporting a vulnerability”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.
What we commit to
Section titled “What we commit to”| 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 |
Everything else
Section titled “Everything else”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.
Verifying downloads
Section titled “Verifying downloads”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.
shasum -a 256 -c SHA256SUMS --ignore-missing