4.4 KiB
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.
- provided information on how to submit a DMCA Counter Notice.
To learn about when and why GitHub may process some notices this way, please visit our README.
Are you the copyright holder or authorized to act on the copyright owner's behalf?
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?
npm.js
Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.
My package capacitor-updater is LGPL-3.0-only licence, and someone has publish it on npm without letting access to the code. i tried to tell them by contacting one person on the team but i didn't get any answer.
Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.
here is the link to the publication https://www.npmjs.com/package/@wisdomgarden/capacitor-updater where it's not possible to see the code they have publish.
my concern is in NPM : https://www.npmjs.com/package/@wisdomgarden/capacitor-updater
that the url who is breaking the copyright of this project :
https://www.npmjs.com/package/@capgo/capacitor-updater
What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.
in the best case it will be preferable to just let them open source the code as it should, but if they can't the best would be to remove it from npm
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.
No
Have you searched for any forks of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.
The fork is in private
Is the work licensed under an open source license?
Yes
Which license?
LGPL-3.0-only now and at the time of the fork AGPL-3.0-only
How do you believe the license is being violated?
the code modified should be published, they didn't publish, in npm it's only the code compiled.
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.
make they github repo as public is the best solution.
What would be the best solution for the alleged infringement?
Other Change
Describe the change.
make they github repo as public to follow agpl requirement
Do you have the alleged infringer’s contact information? If so, please provide it.
yes i did find one person of the team in twitter but, it seems no really active to maybe he never got the message.
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 legal name below to sign this request.
[private]