Skip to content

Added 2025/05/2025-05-13-vmprotect.md #17692

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 14, 2025
Merged

Added 2025/05/2025-05-13-vmprotect.md #17692

merged 1 commit into from
May 14, 2025

Conversation

dmca-sync-bot
Copy link
Collaborator

This is an automated pull request to sync changes from upstream repository.

Diff summary:

A 2025/05/2025-05-13-vmprotect.md

@Copilot Copilot AI review requested due to automatic review settings May 14, 2025 18:48
@dmca-sync-bot dmca-sync-bot merged commit 3115507 into master May 14, 2025
@dmca-sync-bot dmca-sync-bot deleted the updates branch May 14, 2025 18:48
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a new DMCA takedown notice Markdown file syncing upstream changes.

  • Introduces 2025-05-13-vmprotect.md with the full DMCA notice content.
  • Lists infringing repository URLs and incident details.
Comments suppressed due to low confidence (2)

2025/05/2025-05-13-vmprotect.md:1

  • [nitpick] Consider rephrasing 'forks repositories' to 'forked repositories' or 'fork repositories' for grammatical clarity.
Note: Because the reported network that contained the allegedly infringing content was larger than one hundred (100) repositories, and the submitter alleged that all or most of the forks were infringing to the same extent as the parent repository, GitHub processed the takedown notice against the entire network of 1,461 forks repositories, inclusive of the parent repository.

2025/05/2025-05-13-vmprotect.md:5

  • This introductory note appears twice with different repository counts (1,461 vs. 429). Please remove the duplicate or clarify which value is correct.
Note: Because the reported network that contained the allegedly infringing content was larger than one hundred (100) repositories, and the submitter alleged that all or most of the forks were infringing to the same extent as the parent repository, GitHub processed the takedown notice against the entire network of 429 repositories, inclusive of the parent repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant