Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitad95d05

Browse files
author
dmca-sync-bot
committed
Process DMCA request
1 parent39fe4c3 commitad95d05

File tree

1 file changed

+77
-0
lines changed

1 file changed

+77
-0
lines changed

‎2025/12/2025-12-17-clever-craft.md‎

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
**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.**
2+
3+
Yes, I am authorized to act on the copyright owner's behalf.
4+
5+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
6+
7+
No
8+
9+
**Does your claim involve content on GitHub or npm.js?**
10+
11+
GitHub
12+
13+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
14+
15+
I am the[private] for Clever Craft d.o.o.; Clever Craft is a[private] company, we specialize in custom web applications to support enterprise customers. Currently, we work with Hewlett Packard, Hewlett Packard Enterprise, F5 and NetApp. All our agreements and code built by us is in joint ownership with these entities.
16+
17+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
18+
19+
The repositories reported belong to an individual that was hired with a remote B2B contract to Clever Craft d.o.o.; He was in his probation period, undergoing training and received access to repositories for code we manage for Hewlett Packard Enterprise. We have an NDA B2B agreement with this individual, however, during his probation we found that both the passport documents he provided as well as a his company information was fraudulent. Ultimately, we have identified that "[private]" was actually part of the[private] remote worker scheme. The code in the repositories relates to the following Hewlett Packard Enterprise applications:
20+
- Compliance Management application code (internally referred to as ARK, a partner compliance management application)
21+
- New Order Request application code (internally referred to as NOR, an partner order submission form)
22+
- Enrollment (a program enrollment form)
23+
24+
**If the original work referenced above is available online, please provide a URL.**
25+
26+
The applications are not publicly available, they are protected under authorized HPE accounts. If necessary, we are open to have a session to showcase the applications and their code.
27+
28+
**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.**
29+
30+
**Based on the above, I confirm that:**
31+
32+
The entire repository is infringing
33+
34+
**Identify the full repository URL that is infringing:**
35+
36+
https://github.com/RobertTopDev/HPE-NewOrderRequest.git
37+
https://github.com/RobertTopDev/CC-DXP.git
38+
[invalid]
39+
https://github.com/DRukina/CC-DXP
40+
https://github.com/DRukina/HPE-NewOrderRequest
41+
https://github.com/RobertR1223/CC-DXP-code.git
42+
https://github.com/RobertR1223/CC-ARK.git
43+
https://github.com/RobertR1223/HPE-NOR.git
44+
45+
**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <ahref="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.**
46+
47+
No
48+
49+
**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 <ahref="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:**
50+
51+
**Is the work licensed under an open source license?**
52+
53+
No
54+
55+
**What would be the best solution for the alleged infringement?**
56+
57+
Reported content must be removed
58+
59+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
60+
61+
No
62+
63+
**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.**
64+
65+
**I have taken <ahref="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
66+
67+
**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.**
68+
69+
**I have read and understand GitHub's <ahref="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
70+
71+
**So that we can get back to you, please provide either your telephone number or physical address.**
72+
73+
[private]
74+
75+
**Please type your full name for your signature.**
76+
77+
[private]

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp