From e8f49308686fcdcec86a508b7aa115a9a3b95ba5 Mon Sep 17 00:00:00 2001 From: dmca-sync-bot Date: Thu, 9 Jul 2026 20:21:39 +0000 Subject: [PATCH] Process DMCA request --- 2026/07/2026-07-09-aventiv.md | 79 +++++++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+) create mode 100644 2026/07/2026-07-09-aventiv.md diff --git a/2026/07/2026-07-09-aventiv.md b/2026/07/2026-07-09-aventiv.md new file mode 100644 index 00000000000..3eb8de3d750 --- /dev/null +++ b/2026/07/2026-07-09-aventiv.md @@ -0,0 +1,79 @@ +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? 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 an authorized [private] acting on behalf of Aventiv Technologies (and its subsidiary Securus Technologies) to identify, report, and mitigate unauthorized leaks and intellectual property infringements. + +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** + +The infringed work consists of proprietary software, private infrastructure automation scripts, deployment tools, and environment configurations owned exclusively by Aventiv Technologies. This includes internal application source code and deployment specifications (such as AWS EC2 management scripts and environment setups) that are kept strictly confidential and are not authorized for public distribution. + +**If the original work referenced above is available online, please provide a URL.** + +The original work is proprietary corporate software stored securely within Aventiv's internal, private repositories and is not publicly available online. + +**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/TendsToInfinity/laughing-waffle + +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** + +Yes + +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** + +Aventiv Technologies utilizes strict, multi-layered access control mechanisms to safeguard its proprietary source code and infrastructure configurations. Our copyrighted material is hosted exclusively within private, secure repositories and internal corporate environments. Access to these resources requires multi-factor authentication (MFA), strict role-based access control (RBAC), and is limited to authorized personnel via secure corporate networks or virtual private networks (VPNs). These measures effectively prevent any public access, indexing, or unauthorized distribution of our proprietary work. + +**How is the accused project designed to circumvent your technological protection measures?** + +The accused project consists of proprietary files, source code, and configuration data that were exfiltrated or copied from our secure, private internal environments without authorization. By publishing these internal files on a public GitHub repository, the infringer has effectively bypassed our technical access controls (MFA, private repository permissions, and corporate network restrictions), making private intellectual property and sensitive infrastructure details available to the general public and unauthorized actors. + +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and must be identified separately. Please read more about forks. 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:** + +**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 do not have the alleged infringer's direct contact information. We only have the public GitHub username of the account hosting the unauthorized content: TendsToInfinity. + +**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 fair use 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 Guide to Submitting a DMCA Takedown Notice.** + +**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]