Skip to content

Security: c01d43am/Again

SECURITY.md

Security Policy

Supported Versions

We actively maintain and support the latest version of Again. Security updates will be provided for the most recent release.

Version Status Supported
Latest Actively Maintained ✅
Older Versions No Support ❌

Reporting a Vulnerability

If you discover a security vulnerability in Again, please report it responsibly.

How to Report

  • Email: [alugolupawan@gmail.com]
  • GitHub Issues: Open a private security advisory on the GitHub Security tab.
  • PGP Key (if applicable): Encrypt sensitive reports before sharing.

Responsible Disclosure

We request that security researchers:

  1. Do not disclose vulnerabilities publicly until we have had time to investigate and release a patch.
  2. Provide detailed reports with steps to reproduce.
  3. Allow up to 30 days for a response and resolution.

Security Best Practices

  • Keep Again updated to the latest version.
  • Run scans in a controlled and legal environment.
  • Follow ethical hacking guidelines.

Resolved Security Alerts (2024)

  • urllib3 Decompression-bomb safeguards bypassed when following HTTP redirects (High): Fixed in urllib3>=2.0.7. Current: 2.6.3. No direct usage found.
  • Requests Insecure Temp File Reuse in extract_zipped_paths() (Moderate): Fixed in requests>=2.32.0. Current: 2.33.0.
  • Pygments ReDoS due to Inefficient Regex (Low): Fixed in Pygments>=2.18.0. Current: 2.19.2 (transitive via rich).

Dependencies pinned in requirements.txt. No vulnerable code patterns found via codebase search. Dependencies upgraded successfully.

Thank you for helping keep Again secure! 🚀

There aren't any published security advisories