Unauthorized Copy of “Healwright” Published as @testnexus/locatai

[amrsa1]

🏷️ Discussion Type

Bug

Body

I am the creator and copyright owner of the package “Healwright” (https://www.npmjs.com/package/healwright, https://github.com/amrsa1/healwright).

The package @testnexus/locatai (https://www.npmjs.com/package/@testnexus/locatai) and its repository (https://github.com/Divyarajsinh-Dodia1617/LocatAi) are a direct copy of my work, including code, structure, and documentation, without attribution.

The infringing package initially matched my current version (1.7), confirming a full copy. After being confronted, a new version (1.0.0) was released ~6 hours ago, along with minor README wording changes. The repository has also been restricted, suggesting awareness of the violation.

This violates the MIT license, which requires preserving the original copyright notice. I have not authorized this use.
I request review and removal of the infringing package and repository.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Lopesnextgen]

Hey Amr,

This should go through the formal DMCA/copyright process

Sorry you’re dealing with this. If the package is a direct copy of your code/docs and the MIT copyright notice was removed, this is probably not something GitHub Community can resolve from a discussion thread alone.

I’d treat this as a copyright/license compliance issue and file a formal takedown request for both:

• the npm package: @testnexus/locatai
• the GitHub repository: Divyarajsinh-Dodia1617/LocatAi

Before submitting, preserve evidence:

• original package: healwright
• copied package: @testnexus/locatai
• exact copied files
• copied README sections
• version history showing it matched your 1.7
• screenshots of npm pages
• tarball contents from npm, if available
• dates/timestamps
• proof that your MIT copyright notice was removed
• your original repository commits showing authorship

The repository being restricted after confrontation is also worth mentioning, but I’d avoid relying only on that. The strongest evidence is file-by-file similarity and missing license/copyright attribution.

Why this matters

The MIT license allows reuse, copying, modification, and redistribution, but it requires the original copyright and license notice to be preserved.

So the issue is not simply “they forked/copied an MIT project.” The issue is that they allegedly copied and republished it without the required attribution/license notice, and possibly presented it as their own package.

Where to report

Use the official copyright/DMCA route rather than only a community post:

• GitHub DMCA takedown guide: https://docs.github.com/en/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice
• GitHub DMCA policy: https://docs.github.com/en/site-policy/content-removal-policies/dmca-takedown-policy
• npm DMCA policy: https://www.npmjs.com/policies/dmca
• npm unpublish/policy guidance: https://docs.npmjs.com/policies/unpublish/

I would also keep the wording factual and specific:

• “This file is copied from this file”
• “This README section is copied from this section”
• “The original MIT copyright notice is missing”
• “The package was republished under a different name”
• “The repository was later restricted after the issue was raised”

That gives GitHub/npm support a clean trail to review.

Suggested next step

Submit the formal copyright notice with the npm package URL and GitHub repository URL included. Community members can agree that it looks problematic, but actual removal usually requires GitHub/npm to process it through the copyright claims workflow.