Project Ouroboros is an experimental wireless defense & research framework.
We take the security of this project, its contributors, and its community seriously.
Please read below on how to responsibly report vulnerabilities or issues.
Security updates are actively provided for the following branches:
| Version / Branch | Status |
|---|---|
main (Blue Pill) |
β Actively supported |
| Dev branches | |
| Old releases | β Not supported |
If you discover a vulnerability, exploit, or security flaw in Project Ouroboros:
-
Do not open a public GitHub Issue.
Security reports must remain private until triaged. -
Contact us via email:
π§securityouroboros@gmail.comPlease include:
- Description of the issue
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
-
We will acknowledge your report within 72 hours, provide status updates, and coordinate disclosure if required.
- Please allow us a reasonable time (30β90 days) to investigate and patch issues before public disclosure.
- Coordinated disclosure is encouraged β weβll credit valid reporters in release notes unless anonymity is requested.
- We do not support zero-day dumping against this project.
- In-scope:
- Project Ouroboros firmware & code in this repository
- Associated dashboards / APIs we publish
- Out-of-scope:
- Attacks against contributors, maintainers, or third-party dependencies
- Physical attacks on hardware (side-channel, fault injection, etc.)
- Social engineering attacks
Project Ouroboros is provided for research, educational, and defensive purposes only.
Offensive features are intended for controlled environments. Misuse against live networks without consent may violate laws in your country.
We are not responsible for misuse of this project.
We are inspired by the ethos of open security research: sharing knowledge responsibly to make systems safer.
Special thanks to community members and researchers who help improve Ouroboros by reporting issues.