This policy applies to all repositories under the komrad-company GitHub organisation.
If you are unsure whether a finding falls within scope, report it anyway. We would rather triage a false positive than miss a real issue.
Do not open a public GitHub issue for security vulnerabilities.
Report vulnerabilities privately through one of the following channels:
- GitHub private vulnerability reporting (preferred): use the Report a vulnerability button available on each repository's Security tab.
- Direct contact: reach the core team via GitHub. Message @bcaillabet or @wampixel directly.
Please include in your report:
- A clear description of the vulnerability
- The affected repository and component
- Steps to reproduce or a proof-of-concept if available
- Your assessment of impact and severity
- Any suggested remediation if you have one
| Step | Target timeline |
|---|---|
| Acknowledgement of report | 72 hours |
| Initial triage and severity assessment | 7 days |
| Fix or mitigation plan communicated to reporter | 30 days |
| Public disclosure | Coordinated with reporter |
These are best-effort targets. Komrad is currently maintained by a small volunteer team with no dedicated security response function.
We follow a coordinated disclosure model. We ask reporters to:
- Allow us reasonable time to investigate and remediate before public disclosure
- Avoid exploiting the vulnerability beyond what is necessary to demonstrate impact
- Avoid accessing or modifying data that does not belong to you
We commit to:
- Keeping reporters informed throughout the process
- Crediting reporters in the public disclosure unless they prefer to remain anonymous
- Not pursuing legal action against researchers acting in good faith
Komrad is currently in early development. Only the latest commit on the main branch of each repository is actively supported. No stable release versions have been published yet.
Komrad has no registered legal entity at this time. Security reports are handled directly by the core team on a volunteer basis. There is no bug bounty programme.
Last updated: May 2026