What to Do About Copycat Packages on PyPI?

0
8
Asked By CuriousCactus27 On

I recently launched my first package, called repowise, on PyPI. It's a tool for generating and maintaining structured wikis for codebases. However, I noticed this morning that three new packages appeared that all claim to "outperform" my tool, and they even use my package's name in their description. They all popped up around the same time, which feels too coordinated to be a coincidence. Upon further inspection, I've found that they've actually forked my code, made minor changes with an LLM, and released it under new names without giving me any attribution or complying with the AGPL license. Has anyone experienced similar issues with targeted attacks or spam on PyPI? What steps can I take?

5 Answers

Answered By TechExplorer101 On

Yeah, that’s sketchy behavior for sure. Just be cautious because these types of copied packages can sometimes be used for malicious purposes. I’m definitely curious about repowise now—might check it out! Let us know if you need feedback or help.

Answered By NotYourAverageDev On

This kind of thing happens more than you’d think, especially after a package gains some visibility. I’ve had similar experiences where duplicate packages showed up shortly after my own releases. If you report it, you can usually get a resolution pretty quickly—within a couple of days, even. For your peace of mind, definitely take action!

Answered By CodeWanderer88 On

The AGPL rules are quite strict about how your code should be used. If they’re not respecting those terms, you have a solid foundation for taking action against them. Make sure they know you’re aware of it and that you’ve got legal backup.

Answered By SkepticalCoder99 On

That’s really suspicious! It sounds like they might have bots set up to hijack new packages, which has been known to happen on PyPI. But your case is definitely worse since they’ve adapted your actual code! You should definitely look into reporting this to the PyPI security team—they’re often responsive if you fill out their malware form.

Answered By DevilInDetails On

To clarify on the AGPL violation—they took your code, made small adjustments, and released it without attributing you or keeping the original license intact. The AGPL requires that the original author gets credit and that anyone using the code must share their changes under the same license.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.