github/dmca
1
Fork 0
mirror of https://github.com/github/dmca.git synced 2025-06-18 08:55:43 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Process DMCA request

Browse Source
This commit is contained in:
dmca-sync-bot 2024-07-15 20:36:17 +00:00
parent f682cea579
commit b9279be26a
1 changed files with 98 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

98
2024/07/2024-07-15-lodestar.md Normal file
View File

@ -0,0 +1,98 @@
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.**
I am [private], the [private] of Lodestar, located at [private]. My email address is [private], and my telephone number is [private]. Our [private] and [private] is [private], email: [private]
I am contacting you to report the unauthorized use of my copyrighted material. The material in question is the entire JavaScript codebase for our platform, which includes proprietary functions, modules, and algorithms developed exclusively by Lodestar.
**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.**
I am contacting you to report the unauthorized use of my copyrighted material. The material in question is the entire JavaScript codebase for our platform, which includes proprietary functions, modules, and algorithms developed exclusively by Lodestar. The infringing material is available at the following URL(s): https://github.com/BitCoyote/Lodestar-Hub and also referenced from a portfolio site at [private]
The above repository was take from our private company [private] on [private] and posted onto GitHub.
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
The entire repository needs to be removed: https://github.com/BitCoyote/Lodestar-Hub
**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?**
Yes, we have several technological measures in place to control access to our copyrighted content:
1. Version Control Systems: We use [private] for version control to manage and track changes to our codebase. Access to our private [private] is restricted to authorized personnel only.
2. Access Controls: We have implemented strict access controls and permissions within our version control system. Only authorized developers and team members have access to our codebase, and access is granted based on roles and responsibilities.
3. Authentication Measures: Access to our [private] is protected by multi-factor authentication (MFA) to ensure that only verified users can access our code.
4. Internal Policies: We have internal policies and agreements in place that all employees and contractors must adhere to, including confidentiality agreements and code of conduct regarding the handling of proprietary information.
5. Audit Logs: We maintain detailed audit logs of all access and changes to our [private] to monitor and prevent unauthorized access.
**How is the accused project designed to circumvent your technological protection measures?**
The accused project is designed to circumvent our technological protection measures by bypassing our secure access controls and unauthorizedly copying our proprietary code. Specifically:
1. Unauthorized Access: Our code is stored in a private [private] on [private], not on [private]. Access to this [private] is strictly controlled through Google Identity and Access Management (IAM), which ensures that only authorized personnel can access the [private].
2. Controlled Environment: We have implemented robust access controls and authentication measures within [private]. Access is granted only to verified employees and contractors through Google IAM, incorporating multi-factor authentication (MFA) to enhance security.
3. Security Breach: Despite these stringent measures, the accused project has somehow obtained our proprietary code and made it publicly available on GitHub. This action indicates a deliberate attempt to bypass our secure access controls and technological protection measures designed to prevent unauthorized access and distribution.
4. Violation of Internal Policies: All our employees and contractors are bound by confidentiality agreements and internal policies regarding the handling of our proprietary code. The unauthorized publication of our code on GitHub violates these agreements and circumvents our internal security protocols.
These actions undermine our technological protection measures, as the project on GitHub makes our proprietary code accessible to the public without 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 conducted a search for any forks of the allegedly infringing repository on GitHub. Since our proprietary code is hosted on a private [private], this situation is unique. However, upon discovering the unauthorized posting of our code on GitHub, we took the following steps:
1. GitHub Web Interface: We navigated to the infringing repository and viewed the list of forks available through the GitHub web interface.
2. GitHub Search: We used the GitHub search functionality with the query fork:true to filter for forks of the infringing repository.
After conducting these searches, we have found that there are currently no forks of the infringing repository. We will continue to monitor GitHub for any further infringing copies and report them accordingly.
**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]
address: [private]
dob: [private]
[private] signed the Consulting Agreement with Lodestar on [private] and worked with Lodestar until [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.**
[private]
**Please type your full legal name below to sign this request.**
[private]