[aeon_ai]

As some advice to prepare for - if this moves any demand from their enterprise pipeline, the n8n team will be looking for ways to add friction to your life and this project.

The easiest will be giving notice that you’re using n8n in the name of the project, and their lawyers will say that this poses great confusion and false affiliation and besmirches their good name etc. etc.

Not sure it’ll happen, but best be prepared and put some headers in that you’re not affiliated, are a community extension, etc

[cweagans]

I'm not worried about it. If they complain, we can address it then.

[esperent]

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.

[cweagans]

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-