Last week I tried to submit a community node for verification but it failed with:
To be available on cloud, a community node needs to be MIT licensed and have no dependencies.
However it’s already MIT, and the only dependencies it has are those permitted by the guidelines:
n8n-nodes-base and n8n-workflow.
The package I’m trying to submit is https://www.npmjs.com/package/n8n-nodes-pagbank-connect .
Could anyone help me understand if those dependencies are not allowed for real?
Thank you.
PS: I also sent an email to nodes at n8n dot io, 5 days ago, but got no reply.
BramKn
October 15, 2025, 5:41am
2
Have u had a look at the other verified nodes?
The dependencies in the package.json shouldnt be there.
You do not need to add these n8n things as dependencies. So simply remove them.
I do see there is a peer dependency in one of mine, so u might need to add that.
1 Like
Thank you @BramKn . Actually I did, and saw some other official have requirements.
Anyway.. The day after I created this topic, they’ve changed the workflow on the new approvals.
I was able to submit, and test it better with their validation tool, remove all dependencies and submit again with no issues.
Thanks for the hint on checking the other nodes.
1 Like
system
Closed
October 23, 2025, 4:42am
4
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.