Security policy
Many of these projects handle health data or support public services, so security reports are taken seriously and handled privately.
Report a vulnerability privately
Do not report a suspected vulnerability in a public issue, discussion, or pull request. Instead:
- Open the affected project’s repository on GitHub. Each project page links to it under “Source”.
- Choose the Security tab, then “Report a vulnerability”. This sends a private report that only the maintainers can see.
For a problem with this website itself, report it privately on the website repository.
What to include
- a description of the issue and its likely impact;
- the affected project, versions, or commit;
- safe steps to reproduce it; and
- any fix or mitigation you can suggest.
Remove credentials and any personal or patient data from your report. Never include real patient data.
Safety-relevant reports
If the issue could affect patient safety, clinical workflow, or patient-identifiable data, say so clearly, so it can be treated as both a security finding and a potential clinical safety hazard.
Disclosure
We follow coordinated disclosure: the issue is fixed first, then an advisory or release note is published and, if you agree, you are credited. For guidance on running disclosure in your own organisation, see Coordinated Vulnerability Disclosure.
This policy was last reviewed on 21 November 2026.