mirror of
https://github.com/github/dmca.git
synced 2025-06-18 17:05:41 -04:00
Process DMCA request
This commit is contained in:
parent
c8ae9bd67c
commit
9b79a44d85
92
2024/12/2024-12-30-wrusty.md
Normal file
92
2024/12/2024-12-30-wrusty.md
Normal file
@ -0,0 +1,92 @@
|
||||
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 the copyright holder.
|
||||
|
||||
**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.**
|
||||
|
||||
Our company, Wrusty Inc, is the copyright owner of the source code in question (“march_backend”, ). The Work was originally developed by our [private], and we hold all exclusive rights thereto. I am a [private] of the company, authorized to act on behalf of Wrusty in copyright enforcement matters, including filing this DMCA takedown notice.
|
||||
|
||||
**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.**
|
||||
|
||||
The allegedly infringed source code is part of our proprietary “march,” specifically the backend modules responsible for user management and data processing. It is written in Java and contains unique logic developed exclusively by our team.
|
||||
|
||||
Name of the Work (Project Name): march_backend, marchss_frontend
|
||||
Scope/Description: It provides various enterprise-grade features for secure data handling.
|
||||
Original URL: We do not publicly host this code. It is stored privately on our company’s internal Git server and has never been licensed under open-source or public usage terms.
|
||||
This code has been uploaded without authorization to the following [private]:
|
||||
|
||||
[private]
|
||||
[private]
|
||||
|
||||
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
|
||||
|
||||
https://github.com/Steven-Min/march_backend
|
||||
https://github.com/Steven-Min/marchss_frontend
|
||||
|
||||
**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?**
|
||||
|
||||
Enterprise Git Server
|
||||
The source code is stored on enterprise git repository.
|
||||
|
||||
Access Control and Authentication
|
||||
Each developer is assigned a unique user account with specific read/write permissions. Only those who require access for official job duties are granted such permissions.
|
||||
|
||||
Monitoring and Logging
|
||||
All access to the source code repository is logged, and suspicious downloads or activities are investigated immediately.
|
||||
|
||||
**How is the accused project designed to circumvent your technological protection measures?**
|
||||
|
||||
An individual with legitimate internal access (our contractor) appears to have downloaded the code from our [private] while authorized to do so for work purposes.
|
||||
They then uploaded or pushed this code to a public GitHub repository 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.**
|
||||
|
||||
Yes, we have checked the GitHub forks of the infringing repository.
|
||||
|
||||
**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.**
|
||||
|
||||
Name: [private]
|
||||
Email: [private]
|
||||
|
||||
**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.**
|
||||
|
||||
Name: [private]
|
||||
Email: [private]
|
||||
Phone number: [private]
|
||||
Address: [private]
|
||||
|
||||
**Please type your full legal name below to sign this request.**
|
||||
|
||||
[private]
|
Loading…
Reference in New Issue
Block a user