-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Added 2025/06/2025-06-24-google.md #18010
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,106 @@ | ||
Before disabling any content in relation to this takedown notice, GitHub | ||
- contacted the owners of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work). | ||
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). | ||
|
||
To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice). | ||
|
||
--- | ||
|
||
Note: Because the parent repository was actively being forked when this DMCA takedown notice was received, and the submitter had identified all known forks at the time they submitted the takedown notice, GitHub processed the takedown notice against the entire network of 25 repositories, inclusive of the parent repository. | ||
|
||
--- | ||
|
||
**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** | ||
|
||
Yes, I am authorized to act on the copyright owner's behalf. | ||
|
||
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** | ||
|
||
No | ||
|
||
**Does your claim involve content on GitHub or npm.js?** | ||
|
||
GitHub | ||
|
||
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** | ||
|
||
I am [private] at Google. Google is the developer of Play automatic protection, which is a group of technological protection measures (TPMs) that Play app developers can enable to help protect the apps and games they distribute on the Play Store against unauthorized redistribution and piracy. | ||
|
||
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** | ||
|
||
This is not a copyright infringement claim. It is an anti-circumvention claim. | ||
|
||
**If the original work referenced above is available online, please provide a URL.** | ||
|
||
The description of Play automatic protection can be found at https://developer.android.com/google/play/integrity#automatic-protection. | ||
|
||
**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** | ||
|
||
**Based on the above, I confirm that:** | ||
|
||
The entire repository is infringing | ||
|
||
**Identify the full repository URL that is infringing:** | ||
|
||
https://github.com/void-eth/pairip-protection-remover | ||
|
||
**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.** | ||
|
||
Yes | ||
|
||
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** | ||
|
||
Play automatic protection consists of installer checks and anti-tamper protection for apps distributed on Google Play. Installer checks occur at runtime when a user opens an app to verify that the copy of the app on the user's device is not from an unknown distribution channel. Anti-tamper protection, when combined with installer checks, prevents attackers from bypassing the Play developer's distribution or monetization preferences through unauthorized modification, repackaging, redistribution, and piracy. If the checks fail, the user is prompted to get the app on Google Play or the app will not run. | ||
|
||
**How is the accused project designed to circumvent your technological protection measures?** | ||
|
||
The repository contains analysis and information about circumvention of automatic protection. The project provides both the required tooling (actual code in the repo that can circumvent the protection technology) and step-by-step technical instructions (via two [private] video tutorials and instructions in the repo’s readMe file) that can be followed to circumvent the protection technology. | ||
|
||
**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** | ||
|
||
https://github.com/Chalito124/pairip-protection-remover | ||
https://github.com/0x9b42/pairip-protection-remover | ||
https://github.com/0xSMDOZK/pairip-protection-remover | ||
https://github.com/123456789zws/pairip-protection-remover | ||
https://github.com/7k7ped/pairip-protection-remover | ||
https://github.com/cryptoexpertssss/pairip-protection-remover | ||
https://github.com/Familyye/pairip-protection-remover | ||
https://github.com/GameBusuk/pairip-protection-remover | ||
https://github.com/huidaoweilai2024/pairip-protection-remover | ||
https://github.com/iamLazyCode/pairip-protection-remover | ||
https://github.com/jyotidwi/pairip-protection-remover | ||
https://github.com/L364CY-CMD/pairip-protection-remover | ||
https://github.com/ljzlihuan/pairip-protection-remover | ||
https://github.com/notmadcode/pairip-protection-remover | ||
https://github.com/pandurajaking/pairip-protection-remover | ||
https://github.com/poisonflood/pairip-protection-remover | ||
https://github.com/xiamojes/sasasasas | ||
https://github.com/zerty-zert/ppr | ||
|
||
**Is the work licensed under an open source license?** | ||
|
||
No | ||
|
||
**What would be the best solution for the alleged infringement?** | ||
|
||
Reported content must be removed | ||
|
||
**Do you have the alleged infringer’s contact information? If so, please provide it.** | ||
|
||
No | ||
|
||
**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.** | ||
|
||
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** | ||
|
||
**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.** | ||
|
||
**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.** | ||
|
||
**So that we can get back to you, please provide either your telephone number or physical address.** | ||
|
||
[private] | ||
|
||
**Please type your full name for your signature.** | ||
|
||
[private] |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The repository URL on line 77 appears questionable compared to the other URLs listed. Please verify whether 'sasasasas' is the intended repository or if it contains a typo.
Copilot uses AI. Check for mistakes.