PrivacyPuzzle is currently in active development.
| Version | Supported |
|---|---|
| 1.x | ✅ Yes |
| 1.2.0 | ✅ Yes |
If you discover a security vulnerability, please report it responsibly.
- Do not open public GitHub issues for security vulnerabilities.
- Submit a private report including:
- Description of the issue
- Steps to reproduce
- Potential impact
- Suggested mitigation (if available)
Email: 0xlayout@atomicmail.io
- Cryptographic implementation flaws
- Steganographic data leakage
- Authentication or integrity bypasses
- Unsafe default configurations
- Social engineering attacks
- Weak user passwords
- Compromised local environments
- Denial-of-service attacks
PrivacyPuzzle follows these principles:
- Use of established cryptographic primitives
- Native cryptography over third-party implementations
- Minimal attack surface
- Explicit failure on unsafe conditions
- Privacy-by-design approach
Best-effort response targets:
- Initial response: within 7 days
- Triage and assessment: within 14 days
- Fix or mitigation: as soon as reasonably possible
Responsible disclosures may be acknowledged in release notes or documentation at the maintainers’ discretion.
This project is provided as-is, without warranty.
It is intended for educational and research purposes and is not suitable for high-risk or regulated environments.