If you discover a security vulnerability in this project, please report it responsibly.
- β Open a public GitHub issue
- β Share details in forums or discussions
- β Email: hfg1533@gmail.com
- β Include vulnerability details and proof-of-concept
- β Allow 7-14 days for initial response
- β Avoid accessing other users' data
| Stage | Timeline |
|---|---|
| Acknowledgment | 24 hours |
| Initial Assessment | 3 days |
| Fix Development | 7-14 days |
| Security Release | ASAP after fix |
| Public Disclosure | 30+ days after release |
- Code vulnerabilities (RCE, SQL Injection, XSS, etc.)
- Authentication/Authorization flaws
- Cryptographic weaknesses
- Information disclosure
- Denial of Service
- Social engineering
- Physical security
- Third-party vulnerabilities
- Theoretical/low-impact issues
- Missing security headers (unless critical)
- β Always get written authorization before testing
- β Use on systems you own or have permission to test
- β Keep the tool updated to latest version
- β Review scan results before taking action
- β Validate findings independently
- β Sign commits with GPG when possible
- β Follow the Code of Conduct
- β Don't commit secrets or credentials
- β Use secure coding practices
| Version | Status | Support Until |
|---|---|---|
| 3.0.x | Active | Nov 2026 |
| 2.5.x | Security Fixes | Nov 2025 |
| < 2.5 | Unsupported | Ended |
This tool is provided as-is for authorized security testing only. Users are responsible for:
- Obtaining proper authorization
- Complying with applicable laws
- Protecting user data
- Using the tool ethically
Misuse of this tool may violate laws. Use responsibly.
Last Updated: November 2025