ل# Security Policy
Security updates are applied only to the versions listed below. Older versions are not supported and will not receive security patches.
| Version | Supported | Notes |
|---|---|---|
| 1.x.x | ✅ | Active development & patches |
| < 1.0 | ❌ | End-of-life (EOL) |
Note: Replace the version numbers above with the actual release versions of
APZ-MANAGER. If your project uses a different versioning scheme (e.g., semantic versioning, date-based versions), update the table accordingly.
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
To report a vulnerability privately:
- Go to the Security tab of this repository.
- Click "Report a vulnerability" to open a private GitHub Security Advisory.
- Alternatively, you may email the maintainers directly at [INSERT SECURITY EMAIL ADDRESS].
Please include the following details in your report:
- Type of vulnerability (e.g., XSS, SQL injection, privilege escalation).
- Full paths of source file(s) related to the issue.
- Step-by-step instructions to reproduce the vulnerability.
- Any proof-of-concept or exploit code (if possible).
- Impact assessment and potential severity.
We aim to acknowledge receipt of your vulnerability report within 3 business days. After the initial acknowledgment:
- We will investigate and confirm the vulnerability.
- We will develop and test a fix.
- We will release a patched version as soon as possible.
- We will publicly disclose the vulnerability after a fix has been released and users have had time to update.
This security policy applies to the APZ-MANAGER repository and its official releases. Third-party dependencies and services are out of scope for this policy.
We appreciate the efforts of security researchers and users who help keep APZ-MANAGER safe. Responsible disclosures will be acknowledged in release notes unless the reporter requests anonymity.
a