维护者 / Maintainer: M-ing
私密报告邮箱 / Private reporting email: smellrosa@gmail.com
安全修复面向最新稳定版本。旧版本不提供单独的安全修复维护;使用旧版本的用户应升级。仍然欢迎报告旧版本中的问题,维护者会核对最新版本是否受到影响。
Security fixes target the latest stable release. Older versions do not receive a separate security-maintenance stream; users should upgrade. Reports about older versions are still welcome so the maintainer can check whether the latest release is affected.
请把可能造成未授权访问、代码执行、敏感信息泄露等安全问题发送到 smellrosa@gmail.com,不要在公开 Issue、PR 或评论中披露可利用细节。建议邮件标题为 [Security] 简短描述,正文包含:
- 受影响的软件版本、Windows 版本和相关运行环境。
- 问题说明、复现步骤或最小验证样例。
- 可能造成的影响,以及你已经确认的信息。
- 相关截图、日志或代码片段(如有),请先脱敏。
Email potential security issues, such as unauthorized access, code execution or sensitive-data exposure, to smellrosa@gmail.com. Keep exploitable details out of public issues, pull requests and comments. Use a subject such as [Security] Short description and include:
- Affected application version, Windows version and relevant environment.
- A description, reproduction steps or a minimal proof of concept.
- Potential impact and what you have confirmed.
- Relevant screenshots, logs or code snippets, sanitized before sharing.
不要发送密码、访问令牌、私人录制或完整个人数据目录。需要样例时,请使用专门制作的测试数据。
Do not send passwords, access tokens, private recordings or entire personal data folders. Use purpose-made test data for examples.
维护者会尽力确认报告、沟通影响和修复进展,但个人维护项目无法承诺固定响应或修复时限。请在公开漏洞细节前,与维护者沟通披露时间;后续信息可以在同一邮件线程补充。
The maintainer will make a reasonable effort to acknowledge reports and communicate impact and progress. This independently maintained project does not promise a fixed response or resolution time. Please coordinate disclosure timing before publishing vulnerability details, and add follow-up information to the same email thread.
普通故障、界面问题和功能建议请使用 Issues。社区行为投诉请参阅行为准则。本政策使用邮箱接收报告,不依赖 GitHub 私密漏洞报告功能是否开启。
Use Issues for ordinary bugs, UI problems and feature requests. For community conduct concerns, see the Code of Conduct. Email is the reporting channel for this policy regardless of whether GitHub private vulnerability reporting is enabled.