Report a suspected vulnerability privately, never through a public issue or pull request. Email support@massrelay.ai with:
- what you found and where (file, route, or a reproduction),
- the impact as you see it,
- any proof-of-concept you have, redacted of any real credential or personal data.
We acknowledge a report within five working days of receipt, with either a fix timeline or a request for more detail, and we keep you informed until it is closed. We ask you to give us a reasonable window (90 days by default) to fix a confirmed issue before any public disclosure, and we credit you in the fix unless you prefer not to be named. We do not pursue good-faith research that stays within this policy.
Only the latest release and the default branch receive security fixes.
This repository is built to be scanned. .oss-scanner/Dockerfile builds the
community edition from a clean checkout (docker build -f .oss-scanner/Dockerfile .,
no secret and no private registry), and threat_model.md says
what the system protects, where its trust boundaries are, and what is in and out of
scope for a scan. Findings from an automated scan are reported the same way as any
other, to the address above.
In scope: this repository's own code (everything under LICENSE, and the
code under ee/ per its own terms) and the deployment assets it publishes
(deploy/Dockerfile, deploy/compose.dev.yml, .oss-scanner/Dockerfile). Out of scope: the hosted
massrelay.ai services' own operational security (report those the same
address, but treat this file's scope note as descriptive, not a promise of a
bounty), and any third-party project this repository takes code from or
depends on — report those to their own maintainers.
A missing feature, a general hardening suggestion with no exploitable path,
or a report about a dependency with no evidence this repository's own use of
it is reachable — open those as an ordinary issue instead (see
.github/ISSUE_TEMPLATE/bug.md).