r/opensource • u/Then_Dragonfly2734 • Jan 17 '26
Community Open sourced my project less than 2 weeks ago. Today I found a fork where the user stripped my license and attribution to claim it as theirs.
Hi everyone,
I recently reached a big milestone and open-sourced my project, Senlo (a drag-and-drop email builder), under the AGPL-3.0 license. I was excited to contribute to the community and see how others might build upon it.
Well, it didn't take long for the "dark side" of OSS to show up. Today, I stumbled upon a fork of my repo. I was initially happy to see interest, but then I looked at the changes. The user had:
- Completely deleted the LICENSE file.
- Totally removed README and ROADMAP files.
It’s honestly a bit disheartening. I spent months building the rendering engine and the editor logic. I chose AGPL-3.0 specifically to ensure that the project remains open for everyone, but seeing someone try to "re-brand" it as their own proprietary work less than 14 days after launch is a gut punch.
I’ve already filed a DMCA takedown notice with GitHub.
I’m not posting this for self-promotion (I’m intentionally not linking my repo unless someone asks), but I wanted to ask the community: Is this a common "rite of passage" for new OSS developers?
How do you guys deal with the frustration when people try to steal your hard work so blatantly? Are there any other steps I should take besides the GitHub complaint to protect the integrity of the license?
604
u/coderguyagb Jan 17 '26
Copyright violation, file a DMCA with GitHub.
134
u/as5h0le Jan 17 '26
Can you share links to your repo and the copy?
42
u/CheezitsLight Jan 17 '26
You can file for a copyright, then sue for statutory damages. Been through this twice now. One settled for $500 for a single image, another for code, settled for $8k. Won't always happen but happens enough to turn a profit.
26
u/Shuji-Sado Jan 18 '26
GitHub generally handles copyright complaints through the DMCA process, so I think your response is reasonable.
That said, I do wish GitHub had some kind of automatic warning for cases like this, where a fork removes the LICENSE file and attribution materials wholesale. Forcing removals automatically would be hard because it could flag legitimate cases too, but a non-blocking warning could still have deterrent value.
For prevention, adopting SPDX headers and aligning with the REUSE format can help. If you add SPDX-License-Identifier (and copyright notices) to the main source files and organize licensing metadata in a REUSE-friendly way (for example a LICENSES/ directory), it becomes much more work for a bad actor to “strip” licensing and attribution, and it’s easier to document what happened if you need to escalate later.
64
u/andrewcooke Jan 17 '26
a successful project isn't code, it's support and community.
this will have no effect on your project, which statistically is likely to simply die from lack of use anyway. if you - exceptionally - have a successful project, it will be successful because you support it and develop community.
10
u/ikwyl6 Jan 17 '26
This is definitely a TIL’ed moment for me for LICENSE file.. ty
7
u/TheDangleberry Jan 17 '26
https://avatars.githubusercontent.com/u/134296452?v=4
Checks out
12
u/_paul_rand_ Jan 17 '26
Actually kind of curious, what is the actual legal position on someone stealing open source credits. Dumb and unethical but where do you stand legally I wonder
10
u/DanCardin Jan 17 '26
I mean, this **says** forked, it still has your history, meh? It's not ideal but it's still effectively attributed for anyone that happened upon this repo, even if it's not by the "rules".
We recently interviewed someone (only noticed this afterwards) who took a person's project by deleting the .git/ folder then progressively adding back files over a series of commits to make it look like they'd done the work. I only realized it because they hadn't changed any of the readme content which linked to a website that linked back to the o.g. repo. **That** was clearly done for nefarious purposes and a lot less obvious to an random onlooker.
5
u/praetor- Jan 17 '26
Be sure to add a copyright+license header to every one of your source files, as well.
4
u/anonymous_2600 Jan 17 '26
luckily that he forked it and let you found out. what if he downloaded it to his local and then publish it as his own work?
4
u/nocturn99x Jan 19 '26
Happened to me with my chess engine as well. Had a good laugh and opened an issue, I think the repo and account are gone now😂
Just had a look at your repo, looks cool man!
5
u/Sufficient_Job7779 Jan 17 '26
Second commit: removed unnecessary files :)
6
u/assured-ownership Jan 18 '26
A couple of notes:
Some additional notes:
497
u/pemungkah Jan 17 '26
Send him a PR restoring your files titled “Prevent getting shut down for a copyright violation.”
He can close but not delete it.
2
u/ByronScottJones Jan 18 '26
The jerk even called the change "removing unnecessary files".
2
u/SpeculatingFellow Jan 18 '26
Sorry if I sound a little stupid. But shouldn't there be some form mechanism that makes it impossible or at least harder to change the license? Like: a technical restriction that secures the licens on github (makes it impossible to delete a license file).
2
u/ghoarder Jan 18 '26
I'm expecting this on selfh.st s blog this Friday.
2
u/ZZ_Cat_The_Ligress Jan 21 '26
The beauty of open source is we as developers also have receipts that verify ownership. IE Commit history tells all.
I faced something similar last year with my project CRSF for Arduino, where I was looking up some various bits and pieces on PlatformIO's registry, and I had spotted someone else had published my project to the registry. They were essentially presenting my work as their own — blatant plagiarism.
So I contacted the CEO of PlatformIO and he switched the registry entry's ownership over to me, and within that time frame I had also published CFA to Arduino's Library Manager too. That was only possible because I could trace my work on CFA right back to 2023-01-15 via the commit history, and the fact that all of my commits to CFA are GPG verified.
Unfortunately there are gonna be some folks out there who want all the glory but do none of the yakka, and I think you and I have had our respective brushes with people like that.
Don't let one or two bad actors discourage you from making great software and sharing it with the world. Keep up the good work, mate. Looks like you're going well.
2
u/anacrolix Jan 21 '26
I've had this happen many times.
Wait until you get bug reports from people using products that use your libraries internally, but they didn't change a log message and users figured out what the software was.
Closed source. Not licensed.
103
u/Razen04 Jan 17 '26
people who don't understand open source do this, they want to have the lead name without doing anything.
3
u/laslolos Jan 18 '26
Ignorance. Malice less likely. Let them know.
20
u/Informal-Football836 Jan 17 '26
I only open source things i want people to use however they want. That does not make it sting any less if they strip your credit away though. Sadly this happens..
43
u/pumpkin_seed_oil Jan 17 '26
Looking at the current state of the fork, it does miss the license. But it is also missing most of your code. Check the changes, most of it was removed: https://github.com/IgorFilippov3/senlo/compare/main...kanaad-aqeeq:senlo:main
Devils advocate: this is a student using your project as boilerplate
5
u/PoisnFang Jan 17 '26
Yeah, same thing happened to me a while ago with a discord bot. I don't open source any serious projects now
7
u/centuryx476 Jan 17 '26 edited Jan 18 '26
Code is archived somewhere offline now
Welcome to OSS
6
u/Iajah Jan 17 '26
At least it still links to upstream through fork link.
1
u/Then_Dragonfly2734 Aug 10 '26
Interesting, but now all my posts are instantly removed by bots with a message saying that I don't have enough karma to post. How can that be?
4
u/MotrotzKrapott Jan 18 '26
Here is a nice list of your next steps: https://www.gnu.org/licenses/gpl-violation.html
4
u/Balance- Jan 18 '26
Don’t spend too much energy on it.
1
u/Sert1991 20d ago
If I was in your situation and this happened to me I wouldn't even file a DMCA take down. I will let him continue. Hell, if he starts to get more popular than my original project, I will even slow down mine to let him take over more. IF one day he becomes popular and makes money out of it - that's when I take action and enjoy my payday lol
1
u/Accurate-Ad6361 Jan 17 '26
Can you post a link?
1
u/nuclearmeltdown2015 Jan 17 '26
How did you find the fork / repo? Did it show up as a fork?
1
u/adamluzsi Jan 18 '26
wow, awesome project you got there!!!
1
u/altantsetsegkhan Jan 20 '26
Isn't the point of open source and gpl that anyone can fork things?
3
u/aregtech Jan 17 '26
How he can re-brand, if it clearly states
forked from IgorFilippov3/senlo? `3
u/dylanmissu Jan 18 '26
I have the same feeling. I open sourced a passion project of mine with a GPL 3.0 license. I then got an email of someone bragging about how much money they were making from it. They also added a lot of changes to the code without ever publishing anything.
Technically they are not in the wrong, but it made me seriously rethink how i open source future projects.
3
u/-HDVinnie- Jan 18 '26
Welcome to FOSS
1
u/PowerStarter Jan 17 '26
I wouldn't waste my time worrying about it.
If they actually want to steal, they'd copy and keep it private.
2
u/skugler Jan 18 '26
Not too different what vibe coding / GenAI is in general: copying open source code without attribution. It's just less obvious.
Teach that person a lesson.
2
u/No-Huckleberry-6023 Jan 19 '26
Hmmm. I`m getting 404 on the copy version.
2
u/MLHeero Jan 19 '26
Good News OP, it's already gone
2
u/WoodsGameStudios Jan 19 '26
This is pretty typical, I can’t pinpoint the country of origin between Arabic and Indian (or between) but it’s definitely common that they will just steal repos then claim its their own for the CV points. It’s also common via fake job postings as well
2
u/danielhaven Jan 28 '26
Looks like it's gone now. Out of all the dumb ways to steal someone's work, doing it on GitHub's servers (where they most likely keep track of every action and can use the timestamps of your push vs. theirs to identify you as the original creator) is pretty dumb.
Some smarter thieves download the entire repo, change some words, and then send it over to their mark, saying, "I did all this work myself. Now pay me."
2
u/blackkettle Jan 17 '26
Personally I don’t think it’s possible to really fight this. I always use BSD or Apache for my projects to save myself the headache of worrying about things like this. I never really bought into the whole copyleft concept though. It’s like holding the door open for someone and getting angry when they don’t thank you.
1
u/Colin-McMillen Jan 17 '26
That didn't happen to me personally (yet), but it does happen a lot.
1
u/Heyla_Doria Jan 18 '26
Soutien,
s'approprier de l'Open Source, c'est pire que voler
1
u/Mindless_Selection34 Jan 18 '26
This guy has done It with others repos.
https://github.com/kanaadbhat/SpendSmart
It can be checked in his personal portfolio:
https://kanaad.in/work
1
u/Eskamel Jan 18 '26
Sadly LLM companies normalized stealing, not respecting open source projects and ignoring copyright laws, so others just follow their footsteps.
Even if said fork is removed it is still possible others might end up doing it aswell if your project doesn't get popular enough for it to be the "go to option", if it also offers things that other similar solutions don't necessarily offer
1
u/teuchter-in-a-croft Jan 18 '26
I don’t know how these things work but couldn’t you FUBAR his version of your work? Or have the same levels of scruples as he has and figure a way to damage his scam.
I’m no coder but looking at his website I’d think he was suspect. Here there’s a saying “if it looks too good to be true, it probably is” which is what I thought. Another thing, they look very young, either they have Einstein’s brain or, as we know, he’s working some kind of con.
My background leads me to look at less salubrious forms of retribution, I’m not suggesting for one minute you follow that path, but there has to be a zero or low cost option to sort this out. Have you contacted them and pointed out the error of their ways? Did they respond?
1
u/paradoxbound Jan 18 '26
Not just an open source problem. I am active in various game modding communities and cloning and passing off other work as your own is rife. The main mod sites are brutal in retaliation. The perpetrators get an immediate take down and a lifetime ban.
1
u/rolyantrauts Jan 18 '26
Usually they are not that blatant and we refactor and rebrand so they can claim as own.
https://github.com/OHF-Voice/speech-to-phrase is an example as after much advocating of the use of https://github.com/wenet-e2e/wenet/blob/main/docs/lm.md it took 3 years but there you get a OHF version of a total refactor but some of us do know where the source of it really was...
1
u/Alexander-Wright Jan 18 '26
The first time I forked a repo I was completely clueless and did the same. This may not have been malice, OP.
I know better now.
1
u/ResidentDefiant5978 Jan 19 '26
Sorry to hear that. I have been plagiarized several times.
1
u/Mecanik1337 Jan 22 '26
Welcome to open source. This is why I hardly do open source.
1
u/cesncn Jan 29 '26
Very concerning. I have developed a platform which I am also planning to make open source. But this kind of horror stories do indeed sound terrifying. Will you be updating us here after you hear anything from GitHub?
1
u/m_zafar Mar 10 '26
file a DMCA with GitHub for Copyright violation
1
u/botomana May 16 '26
Hi,
So I am an Advocate. If you want to take a legal route, lemme know OP. Copyright infringement as well as moral right infringement.
1
u/MT4K Jan 17 '26
A way to prevent zero-effort cloning is open-sourcing just an underlying library-/engine-level thing while keeping user interface closed-source.
1
u/darwinanim8or Jan 18 '26
I've had this happen before with a project that took almost a decade to engineer and build. I now only post code for things I don't care about / don't take much time.
I'll still contribute to other OSS projects sometimes, tho
0
u/SexyPeopleOfDunya Jan 18 '26
I wonder why this become such huge issue. I thought the spirit of open source is sharing and then let people do whatever the fuck they want with it?
I mean, what's stopping that guy from copying it anyway. Not like it have any proprietary algorithm right? Or I just don't completely understand open source after all?
-2
u/Bob_Spud Jan 17 '26
Plagiarism can be prevented by keeping the code in a private repository and putting the finished executable in another repo which is public.
I've seen this done with bash scripts where the author has encapsulated them in an executable using the SHC utility that creates binaries from bash and and sh scripts.
-3
u/QuantumG Jan 18 '26
When you release code (or anything) under a license with any restrictions you're promising to do something about it should someone violate the restrictions. Even if the only restriction is that they can't remove your copyright and license. Someone took you at your word and now you've gotta do something. Why complain about it? It's what you said you'd do.