请优先使用本仓库 GitHub 页面中的 Security → Report a vulnerability 提交私密报告。不要在公开 Issue、讨论区或 Pull Request 中披露可利用细节。

如果私密漏洞报告入口不可用，可以创建一个不含漏洞细节的公开 Issue，询问维护者提供私密沟通渠道。

报告请尽量包含：

• 受影响版本和 APK 来源；
• 设备 Android/One UI 版本；
• 风险、攻击前提和可能影响；
• 最小复现步骤或概念验证；
• 建议修复或缓解措施；
• 是否已经向其他人披露。

请勿提交真实通知正文、联系人或群名、设备序列号、账号信息、私钥、密码或未经脱敏的截图。

维护者会确认收到报告、验证影响、准备和测试修复，并在适当时通过 GitHub Security Advisory 协调披露。安全修复的发布时间取决于风险和验证范围；本项目目前不承诺固定响应时限。

官方 v0.4.0 发布资产为：

priority-ringer-v0.4.0.apk

官方发布证书 SHA-256：

DE99C7576128AB859EDF6D45E15162AAD5274CAEEE52D16843D0ED7D42F8A4BC

每个 Release 还必须公布该 APK 自身的 SHA-256。证书指纹只能确认签名身份，APK 哈希用于确认具体文件；两者都应核对。

从源码生成的本地 APK 使用构建者自己的本地密钥，不是官方发布包，也通常不能覆盖安装官方版本。不要提交或上传 .local、密钥库、密码文件或 CI 临时签名材料。

本应用需要敏感的通知读取权限。授权后，Android 可向它提供当前资料空间中的通知。应用不申请 Internet 权限，不执行来源通知中的 PendingIntent，也不申请通讯录、无障碍、麦克风或相机权限。完整数据边界见 PRIVACY.md。

以下情况通常不是安全漏洞，但仍欢迎作为普通 Bug 报告：

• 来源应用没有公开足够通知身份；
• Samsung 电池策略停止监听服务；
• DND、蓝牙或其他音频策略阻止声音；
• 启发式来电识别产生兼容性问题。

Prefer Security → Report a vulnerability on this repository's GitHub page. Do not disclose exploitable details in a public Issue, Discussion, or Pull Request.

If private vulnerability reporting is unavailable, open a public Issue without vulnerability details and ask the maintainers for a private contact channel.

Please include when possible:

• affected version and APK source;
• device Android/One UI version;
• risk, prerequisites, and possible impact;
• minimal reproduction steps or proof of concept;
• suggested fix or mitigation;
• whether the issue has been disclosed elsewhere.

Do not submit real notification content, contact or group names, device serial numbers, account data, private keys, passwords, or unredacted screenshots.

Maintainers will acknowledge the report, validate impact, prepare and test a fix, and coordinate disclosure through a GitHub Security Advisory when appropriate. Timing depends on risk and verification scope; this project currently makes no fixed response-time commitment.

The official v0.4.0 release asset is:

priority-ringer-v0.4.0.apk

Official release certificate SHA-256:

DE99C7576128AB859EDF6D45E15162AAD5274CAEEE52D16843D0ED7D42F8A4BC

Each Release must also publish the SHA-256 of that specific APK. The certificate fingerprint identifies the signing identity, while the APK hash identifies the exact file; verify both.

A locally built APK uses the builder's own local key. It is not an official release and normally cannot update an installed official build. Never commit or upload .local, keystores, password files, or temporary CI signing material.

This app requires sensitive notification access. Once granted, Android can supply notifications from the current profile. The app does not request Internet access, invoke source-notification PendingIntent objects, or request contacts, accessibility, microphone, or camera access. See PRIVACY.md for the full data boundary.

The following are usually compatibility bugs rather than security vulnerabilities, but are still welcome as ordinary Bug reports:

• a source app does not publish enough notification identity;
• Samsung battery policy stops the listener;
• DND, Bluetooth, or another audio policy suppresses sound;
• heuristic call classification is incompatible with a source app.