Added 2026/09/2026-09-09-source-code.md

2026/09/2026-09-09-source-code.md

@@ -0,0 +1,123 @@
+Before disabling any content in relation to this takedown notice, GitHub
+- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
+- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
+
+To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
+
+---
+
+**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.**
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The copyrighted work in question is the source code, design, layout, and unique tracking assets for [private] [private] [private] portfolio, accessible live at [private] and hosted publicly in [private] GitHub repository: [private]
+
+1.  Timeline & Priority of Creation
+
+Original Work Created: Initial commits for [private] original repository ([private]) date back to February 15, 2021, documenting the complete build history, package.json updates, and deployment setups.
+
+Infringing Work Created: The infringing repository (Ajayleo11/personal-portfolio) was created on June 29, 2026\. The user copied [private] code and uploaded it as a brand-new repository in an attempt to wipe the original Git commit history.
+
+1.  Direct Technical Proof of Plagiarism    
+    The infringing repository and its live deployment at [private] contain unedited copies of [private] proprietary files and tracking identifiers:
+
+Google Analytics Tag: The source code of his deployed site directly embeds [private] [private] Google Tag Manager script and Measurement ID ([private]). Traffic from his site ([private]) logs directly into [private] Google Analytics dashboard under [[private]]
+
+Personal Favicon Asset: His source code links directly to /assets/images/ht.svg—which contains [private] [private] ([private]).
+
+Codebase & Design: The overall Angular, SCSS, and TypeScript architecture is an unauthorized duplicate of [private] website [private]
+
+1.  Location of Original & Infringing Material
+
+Original Website: [private]
+
+Original GitHub Repository: [private]
+
+Infringing GitHub Repository: https://github.com/Ajayleo11/personal-portfolio
+
+Infringing Live Site: [private]
+
+**If the original work referenced above is available online, please provide a URL.**
+
+[private]  
+[private]
+
+**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/Ajayleo11/personal-portfolio
+
+**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints]([https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology%22%3EComplaints](https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology%22%3EComplaints)) about Anti-Circumvention Technology if you are unsure.**
+
+No
+
+**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.</a]([https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork%22%3Eforks.%3C/a)>](https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork%22%3Eforks.%3C/a)%3E) 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?**
+
+Yes
+
+**Which license?**
+
+mit-license
+
+**How do you believe the license is being violated?**
+
+The MIT License explicitly mandates the following condition:
+
+"The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."
+
+The infringer (Ajayleo11) breached the terms of the MIT License in the following ways:
+
+Removal of Attribution & License File: The user completely stripped my copyright notice (Copyright (c) 2021 [private]) and removed the original LICENSE file from their repository.
+
+False Claims of Ownership: The user re-uploaded the source code into a brand-new repository (Ajayleo11/personal-portfolio) to wipe the original Git commit history and falsely claimed sole authorship of the project.
+
+Unauthorized Copying of Personal Brand Assets: The MIT License does not extend rights to personal brand identifiers. The infringer copied [private] [private] logo asset (ht.svg, representing [private]) and embedded [private] unique Google Analytics tag ([private]), causing live traffic from their deployment ([private]) to stream into [private] analytics dashboard.
+
+Because the required conditions of the MIT License were violated, the infringer's right to use, host, or distribute this codebase has been legally revoked.
+
+**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**
+
+To bring the project into full compliance with the original MIT License, the user (Ajayleo11) must fulfill the following mandatory requirements:
+
+Restore Legal Attribution & License File: Add the original LICENSE file back to the repository containing the exact copyright notice (Copyright (c) 2021 [private]) and full MIT license text.
+
+Provide Clear Attribution & Source Links: Include prominent credit in the README.md and live website UI acknowledging that the project is derived from [private] original work, complete with backlinks to [private] GitHub repository ([private]) and [private] portfolio [private]. Ideally, the project should be created as an official public Fork of [private] original repository rather than an untracked re-upload.
+
+Remove Personal Identifying Assets & Tracking IDs: Strip out [private] [private] brand logo (ht.svg), update the site branding to avoid impersonation, and remove [private] personal Google Analytics tracking tag ([private]) from all source files and deployed hosting environments.
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+**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]([https://www.lumendatabase.org/topics/22%22%3Efair](https://www.lumendatabase.org/topics/22%22%3Efair)) 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]([https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/%22%3EGuide](https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/%22%3EGuide)) 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]