My non-lawyer understanding is that this issue can be reduced by not having the copyrighted name first. So n8n-Oidc might get you flagged, but Oidc-n8n should be fine.
I'm reasonably sure that it's not a hard-and-fast rule. As an easy counterexample, they actively encourage people to publish stuff prefaced with n8n: https://www.npmjs.com/search?q=n8n-nodes-
I meant based on copyright law. I have looked it up before and that's the general consensus I saw.
Basically, if you name your project starting with a copyrighted name like "Android Firewall" and you receive a legal request to change it, you should probably do so. But if your project is "Firewall for Android", the legal request is probably just trying to scare you, ignore it.
If n8n specifically says they're ok with this kind of name then it's ok, of course.
Comments
My non-lawyer understanding is that this issue can be reduced by not having the copyrighted name first. So n8n-Oidc might get you flagged, but Oidc-n8n should be fine.
I'm reasonably sure that it's not a hard-and-fast rule. As an easy counterexample, they actively encourage people to publish stuff prefaced with n8n: https://www.npmjs.com/search?q=n8n-nodes-
I meant based on copyright law. I have looked it up before and that's the general consensus I saw.
Basically, if you name your project starting with a copyrighted name like "Android Firewall" and you receive a legal request to change it, you should probably do so. But if your project is "Firewall for Android", the legal request is probably just trying to scare you, ignore it.
If n8n specifically says they're ok with this kind of name then it's ok, of course.