Applies to every repository in this organisation.
Do not open a public issue for a security problem.
Use GitHub's private vulnerability reporting on the affected repository: Security → Report a vulnerability. It is enabled org-wide and goes straight to the maintainers.
If it is disabled or you cannot reach it, contact the maintainer privately using
the address on their GitHub profile, with SECURITY in the subject.
Please include:
- what the issue is, and which repo and version
- steps to reproduce, ideally a minimal case
- what an attacker gains
- any suggested fix
| First response | within 7 days |
| Assessment and plan | within 14 days |
| Fix for a confirmed high-severity issue | as fast as we reasonably can, prioritised over feature work |
We will keep you updated, credit you when the fix ships unless you prefer otherwise, and let you know if we decide something is not a vulnerability — along with why.
In scope:
- The code in these repositories.
- Credential or key handling in the clients and MCP servers — in particular any path where an API key could leak into logs, error messages, telemetry or a model's context.
- Injection through record content, including prompt injection reaching an LLM or an agent via record text in the MCP servers and the chat app.
- Anything causing a tool to disclose more than the upstream API authorises.
Out of scope:
- The upstream dataset and epsteinexposed.com itself. We are a client. Report those to that service.
- Vulnerabilities in dependencies with no exploitable path through our code — though we do want to hear about them; open a normal issue.
- Rate limiting or availability of the upstream API.
A bug that causes a tool to expose personal information beyond what the upstream records authorise — leaking a victim's identity, joining data the tools should not join, or exposing a user's own uploaded contact list — should be reported through this private channel, not a public issue. It will be treated with the same priority as a conventional vulnerability.
If you are named in the records and believe a record is wrong, that is not a
security issue and we cannot fix it — see
CONTRIBUTING.md for where it goes.
The latest release of each package receives security fixes. These are young projects; there are no long-term support branches.