зеркало из https://github.com/github/dmca.git
94 строки
4.7 KiB
Markdown
94 строки
4.7 KiB
Markdown
|
Before disabling any content in relation to this takedown notice, GitHub
|
|||
|
|
- contacted the owners of some or all of the affected npm packages to give them an opportunity to [unpublish the package](https://docs.npmjs.com/unpublishing-packages-from-the-registry).
|
|||
|
|
- 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).
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
|
|||
|
|
|
|||
|
|
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?**
|
|||
|
|
|
|||
|
|
Both
|
|||
|
|
|
|||
|
|
|
|||
|
|
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
|
|||
|
|
|
|||
|
|
We found that the copyrighted proprietary development documents owned by our company that were not published before are now disclosed on your platform, so there is an urgent need for control. I am acting on behalf of the [private] of our company.
|
|||
|
|
|
|||
|
|
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
|
|||
|
|
|
|||
|
|
This code base is used as a type declaration file for the api and built-in methods of the Douyin-microapp. It has not been made public before. At present, it is found that the code of this content has been published on github & npm without permission.
|
|||
|
|
At the same time, in this code, the user pasted the [private] used internally by ByteDance. As you can see, the package name of his also contains bytedance (our company signature), which proofs that it is copied from us.
|
|||
|
|
|
|||
|
|
[private]
|
|||
|
|
[private]
|
|||
|
|
|
|||
|
|
Below is screenshot comparison:
|
|||
|
|
|
|||
|
|
[private]
|
|||
|
|
[private]
|
|||
|
|
[private]
|
|||
|
|
[private]
|
|||
|
|
|
|||
|
|
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
|
|||
|
|
|
|||
|
|
github address: https://github.com/yeliex/bytedance-microapp-typings
|
|||
|
|
npm address: https://www.npmjs.com/package/bytedance-microapp-typings
|
|||
|
|
|
|||
|
|
**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?**
|
|||
|
|
|
|||
|
|
This copyrighted file has been set with permission of access to only a limited number of people within our company, so it must be either leaked or cracked.
|
|||
|
|
|
|||
|
|
**How is the accused project designed to circumvent your technological protection measures?**
|
|||
|
|
|
|||
|
|
It enables the public to access the copyrighted file and use it without our authorization.
|
|||
|
|
|
|||
|
|
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
|
|||
|
|
|
|||
|
|
No, not to our knowledge.
|
|||
|
|
|
|||
|
|
**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]
|
|||
|
|
[private]
|
|||
|
|
|
|||
|
|
**Please type your full legal name below to sign this request.**
|
|||
|
|
|
|||
|
|
[private]
|