| Version | Supported |
|---|---|
Latest release (3.x) |
✅ |
< 3.0 |
❌ |
Do not post vulnerability details, exploit payloads, or sensitive reproduction steps in public GitHub Issues or public threads.
- Private Advisory (preferred): If enabled on the repository, submit a private report via GitHub Security Advisories.
- Direct / Coordination Contact: Reach the maintainer via LinkedIn, GitHub (@AlexTkDev), or open a coordination note in GitHub Discussions without disclosing technical vulnerability details publicly so a private channel can be arranged.
When reporting privately, include:
- affected MacOSCleaner version (or commit) and macOS version
- description of the vulnerability
- minimal reproduction steps
- security impact
- logs or screenshots (if applicable)
Please allow a reasonable remediation window (up to 90 days for complex issues) before any public disclosure so a fix can be released for users.
The maintainer will not initiate legal action against researchers who discover and report vulnerabilities in good faith in accordance with this policy, provided testing is performed solely on your own local devices and accounts, does not access or destroy third-party data, does not disrupt services, and avoids public disclosure prior to coordination.
This document does not modify the project license.
See LICENSE for licensing terms.