Currently supported versions with security updates:

We take security vulnerabilities seriously. If you discover a security issue, please follow these steps:

Please do not report security vulnerabilities through public GitHub issues.

Send your report to:

• GitHub Security Advisories: Use the private vulnerability reporting feature
• Email: Create a private disclosure (recommended for critical issues)

Please provide:

• Type of vulnerability
• Full path of source file(s) related to the issue
• Location of affected source code (tag/branch/commit)
• Step-by-step instructions to reproduce
• Proof-of-concept or exploit code (if available)
• Impact assessment
• Suggested fix (if any)

• Initial Response: Within 48 hours
• Status Update: Within 7 days
• Fix Timeline: Critical issues within 30 days

1. Run with Appropriate Privileges

   # Only use sudo when necessary
   sudo python3 main.py

2. Keep Dependencies Updated

   pip install --upgrade -r requirements.txt

3. Verify Source

   # Always clone from official repository
   git clone https://github.com/U-C4N/Wif-G.git

4. Review Permissions

   • Port scanning may require firewall exceptions
   • Network modifications need admin rights
   • Be cautious with optimization features

1. Code Review

   • All PRs require review before merge
   • Security-sensitive changes need extra scrutiny

2. Dependency Scanning

   # Check for known vulnerabilities
   pip install safety
   safety check

3. Static Analysis

   # Security linting
   bandit -r src/

4. Input Validation

   • Always validate user inputs
   • Sanitize command-line arguments
   • Prevent injection attacks

• Port scanning may trigger IDS/IPS alerts
• Some networks block or rate-limit scanning
• Ensure you have permission to scan the network

• Tool requires sudo for full functionality
• Minimal privilege principle applied where possible
• Root operations clearly documented

• No sensitive data is stored permanently
• Network credentials are never collected
• Temporary files cleaned up on exit

We believe in responsible disclosure:

1. Report the vulnerability privately
2. Allow reasonable time for fix development
3. Coordinate public disclosure timing
4. Credit researchers appropriately (if desired)

Security patches are released as:

• Critical: Immediate patch release
• High: Within 7 days
• Medium: Next minor version
• Low: Next major version

We appreciate security researchers who help keep Wif-G safe:

• [List will be updated as reports come in]

• OWASP Top 10
• CWE Top 25
• Python Security Best Practices

Last Updated: 2025-01-28