Process DMCA request

Author: dmca-sync-bot

2026/04/2026-04-06-providernow-2.md

@@ -0,0 +1,101 @@
+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 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.**
+
+My name is [private], and I am the [private], [private], and [private] of ProviderNow, the entity of note. I have read and understand GitHub's Guide to Filing a DMCA Notice.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The copyrighted work consists of proprietary software source code and related materials owned by ProviderNow, including application code, system architecture, APIs, business logic, and associated assets used to operate our healthcare technology platform.
+
+This codebase was originally developed and maintained in [private] [private] within Azure DevOps and secured infrastructure hosted on Microsoft Azure. Access to this material was restricted to authorized personnel only and protected by authentication, role-based permissions, and confidentiality obligations.
+
+The infringing content located at: https://github.com/ProviderNowProviderNow/pauli, appears to be an unauthorized copy of our proprietary codebase that was obtained without permission and publicly distributed in violation of our ownership rights and applicable agreements.
+
+ProviderNow is the rightful owner of this copyrighted work, and this material has not been authorized for public release, distribution, or reproduction.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+providernow.org
+
+**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/ProviderNowProviderNow/pauli
+
+**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?**
+
+We employ commercially reasonable and industry-standard technological measures to control access to and protect our copyrighted materials, including proprietary source code, content, and system assets.
+
+Access to such materials is strictly restricted through authenticated user accounts and role-based access control (RBAC), ensuring that only authorized personnel with a legitimate business need may access specific repositories or resources. All proprietary code and materials are maintained within secured, private environments hosted in Azure DevOps and protected within infrastructure managed through Microsoft Azure.
+
+We enforce the principle of least privilege and require secure authentication measures, including multi-factor authentication where applicable. Access rights are periodically reviewed and promptly revoked upon role changes or termination. All access and activity are logged and auditable, including version history, user actions, and modifications to protected materials.
+
+In addition, we utilize encryption of data in transit and at rest, network-level security controls, and environment-level access restrictions within our cloud infrastructure. These measures are designed to prevent unauthorized access, copying, or dissemination of our copyrighted materials.
+
+Unauthorized access, reproduction, or distribution of our materials is expressly prohibited by internal policy, contractual agreements, and applicable law. Collectively, these technological safeguards effectively control access to our protected works and support enforcement against unauthorized use or infringement.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+The accused project does not reflect a legitimate or authorized access pathway, but rather the circumvention of our technological protection measures through misuse of authorized credentials and subsequent unauthorized distribution.
+
+Our copyrighted materials are protected within private repositories in Azure DevOps, with access restricted by authenticated user accounts, role-based access controls, and confidentiality obligations. These measures are designed to prevent public access and unauthorized copying.
+
+The infringing material appears to have been obtained by an individual who previously had authorized access under contractual and confidentiality restrictions. That individual then exceeded and violated those restrictions by extracting the protected codebase and publishing it publicly.
+
+By removing the code from its secured environment and distributing it on a public platform, the accused project effectively bypasses and nullifies our access controls, authentication requirements, and repository protections, thereby circumventing the technological measures in place to control access to our copyrighted work.
+
+**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:**
+
+**Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent 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.**
+
+They used multiple different emails. [private], [private], [private], [private], goes by the name of [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 name for your signature.**
+
+[private]