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

Merge pull request #17832 from github/updates

Browse Source 
Added 2025/06/2025-06-10-lark.md
This commit is contained in:
DMCA Sync Bot 2025-06-10 08:20:16 -07:00 committed by GitHub
commit 10e587de5c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 89 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

89
2025/06/2025-06-10-lark.md Normal file
View File

@ -0,0 +1,89 @@
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).
---
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 5 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 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.**
[private] of ByteDance.
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
We, ByteDance. and the affiliated companies including LARK TECHNOLOGIES PTE. LTD. (hereinafter referred to as “Our Company”) have earned immense goodwill and reputation through the development and operation of the mobile application "Lark" since the year 2019. Our Company are owners and/or authorized rights holders for the relevant intellectual property rights, including our copyright in the source code of Lark App and trademark rights in the "Lark" wording mark.
The disputed repo disclosed Lark source code. For example, the following link https://github.com/skyasker/iOS-client/blob/3f6eff648c854ae7218b517b1bcf71672c269a26/bin/verifyAppSize/commonFuntion.py#L39 leaked the internal endpoint of ByteDance and the secret of Lark.
**If the original work referenced above is available online, please provide a URL.**
Our Lark App iOS version can be found here: https://apps.apple.com/us/app/lark-team-collaboration/id1452166623.
**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/lark-opensource/iOS-client
**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?**
All scripts and functions are highly encrypted in the web client, and several methods are applied to anti-reverse engineering.
**How is the accused project designed to circumvent your technological protection measures?**
It directly reversed all core logics, including encryption methods and data report methods, of our message product named "feishu-ios".
**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/SomenLenk/iOS-client
https://github.com/skyasker/iOS-client
https://github.com/GIKICoder/iOS-client
https://github.com/Alvazz/iOS-client
**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. We found no contact info of the repo owner. We therefore request GitHub to disclose the owner's contact info.
**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]