The Compose Call Guard team takes the security and privacy of our users seriously.
| Version | Supported |
|---|---|
| 2.0.x | ✅ |
| < 2.0 | ❌ |
If you discover a security vulnerability in this project, please do NOT open a public issue. Publicly disclosing a vulnerability can put user privacy at risk.
Instead, please report security concerns privately through one of the following methods:
- GitHub Private Vulnerability Reporting: Go to the Security tab of this repository and click Report a vulnerability.
- Direct Security Contact: Email the maintainer at
me@andrewwangdev.comwith the subject[SECURITY] Compose Call Guard Vulnerability Report.
- A detailed description of the vulnerability.
- Steps to reproduce or proof-of-concept (PoC) code.
- Impact assessment (e.g., call log leakage, bypass of blocking rules).
We will make every reasonable effort to review, acknowledge, and investigate your report as promptly as feasible.
Note
Because this repository is in a completed and archived state, no guaranteed response timeline or fixed SLA (such as 24 or 48 hours) is committed. Confirmed critical vulnerabilities will be addressed with high priority.