Skip to content

dmca-abuse-template.md

Latest commit

 

History

History
158 lines (110 loc) · 6.62 KB

dmca-abuse-template.md

File metadata and controls

158 lines (110 loc) · 6.62 KB

GitHub DMCA / Abuse 提报模板（AGPL-3.0）

用于针对仿冒仓库、搬运仓库、带毒二进制仓库进行快速提报。

适用对象：

  • 我方为版权方（或版权方授权代表）
  • 原项目采用 AGPL-3.0
  • 对方仓库存在未合规分发、伪装发布、恶意样本风险

官方入口

建议两条都提：DMCA 处理版权，Abuse 处理安全风险。

提报前准备清单

  1. 原仓库 URL（官方仓）
  2. 被举报仓库 URL（侵权仓）
  3. 侵权样本下载 URL（Release 链接）
  4. 样本哈希（SHA256）
  5. 检测结论（如 QVM.Gen.196650）与检测报告文件
  6. AGPL-3.0 违反点（源码提供、修改说明、许可声明等）
  7. 联系方式（姓名、邮箱、地址、电话）

DMCA 表单逐项模板

以下字段按 GitHub 表单常见问题顺序整理，可直接复制。

Are you the copyright holder or authorized...?

Yes, I am the copyright holder.

如为代理：

I am authorized to act on behalf of the copyright owner.

Please describe the nature of your copyright ownership...

I am the copyright owner of the original MaaNTE source code, associated release artifacts, and accompanying documentation, and I hold the exclusive rights to reproduce, distribute, and prepare derivative works. I have not authorized the repository identified in this notice to copy, publish, or distribute those copyrighted materials.

Please provide a detailed description of the original copyrighted work...

The original copyrighted work is the MaaNTE project, which is copyrighted by us and released under the GNU Affero General Public License v3.0 (AGPL-3.0). Our work includes the source code, build and packaging scripts, task/pipeline definitions, UI assets, and release artifacts. AGPL-3.0 allows copying and redistribution only if license conditions are met, including preservation of copyright and license notices, clear notice of modifications, and provision of the complete corresponding source code for distributed binaries (including required build/install scripts), and, where applicable, source availability to remote network users under AGPL Section 13. The reported repository/release reproduces and distributes our copyrighted work (or derivative work) without satisfying these AGPL-3.0 conditions, so the distribution is unauthorized.

If the original work ... is available online, please provide a URL.

https://github.com/1bananachicken/MaaNTE
https://docs.maante.org

Entire repository or specific files?

整仓侵权时使用：

Based on the above, I confirm that the entire contents of the repository are infringing.

Identify the full repository URL that is infringing:

https://github.com/<user>/<repo>

Do you claim to have any technological measures...?

No. This notice is based on copyright/license infringement (AGPL-3.0 non-compliance), not anti-circumvention.

Forks 字段

  • 未逐个核查时：
None at this time. I am currently reporting only the parent repository. If infringing forks are identified, they will be submitted separately.
  • 仅当 fork 网络超过 100 且你确实抽样核查后，才使用 “all or most forks are infringing” 语句。

Is the work licensed under an open source license?

Yes.

Which license?

优先选择 GNU Affero General Public License v3.0 (AGPL-3.0)。
若表单下拉没有 AGPL，选择最接近项并在后续描述中明确写 AGPL-3.0。

How do you believe the license is being violated?

I believe the license is being violated because the repository and its release artifacts distribute a modified/repackaged version of our AGPL-3.0 work without complying with AGPL conditions. In particular, the distribution does not provide the complete corresponding source code for the exact binaries being distributed, does not provide clear/prominent notices of modifications and provenance, and does not preserve required license/copyright notices in a compliant manner. As a result, the redistribution is outside the scope of AGPL-3.0 permissions (including obligations under AGPL v3 sections 4–6, and section 13 where applicable).

What changes can be made to bring the project into compliance...?

To bring the project into AGPL-3.0 compliance, the maintainer must do one of the following:
1) Remove all infringing content and release artifacts; or
2) Fully comply with AGPL-3.0 for all distributed binaries by:
- Publishing the complete corresponding source code for the exact released binaries (including build/install scripts and required dependencies/instructions).
- Keeping copyright notices and including the full AGPL-3.0 license text.
- Clearly marking all modifications and their dates, and identifying upstream origin.
- Providing prominent notice in the repository and releases that the work is AGPL-3.0 licensed and where the source can be obtained.
- If the software is used over a network, providing source access to remote users as required by AGPL-3.0 Section 13.
Until these conditions are met, distribution of the current repository/release artifacts should stop.

Do you have the alleged infringer’s contact information?

Only public contact information is known:
- GitHub username: <user>
- Profile: https://github.com/<user>
- Repository: https://github.com/<user>/<repo>
I do not have verified private contact details (email/phone/address).

Abuse Report 附加模板（带毒产物）

用于强调“发布产物存在恶意风险”，建议和 DMCA 同时提交。

The repository release artifact appears malicious based on security testing.
The tested sample SHA256 is <sha256>, and it was detected by a security engine as: QVM.Gen.196650 (generic malware detection).
Please review and take action under GitHub’s Active Malware/Abuse policies.

中文版可用：

仓库产物存在安全风险。我们对该仓库发布的可执行文件进行了检测，样本 SHA256 为 <sha256>，被安全引擎检出为：QVM.Gen.196650（恶意程序泛型检测）。请 GitHub 按 Active Malware/Abuse 政策复核并处置相关发布内容。

归档建议

每次提报后，建议在内部记录：

  • 提报时间（UTC+8）
  • 目标仓库 URL
  • 样本 SHA256
  • 工单编号（GitHub 返回）
  • 当前状态（submitted / follow-up / resolved）

这份模板可直接复制到新案件，按 <...> 占位符替换即可。