Just starting a discussion There are a number of useful contrib nodes that end up not being maintained How about copying them into the official Node-RED sphere? But obviously too much work for core devs so I thought, why not have another level in between a node-red-node and a node-red-contrib no…

[image] TotallyInformation: There are some really valuable thoughts in this thread Yes agree, and having experienced this issue a number of times it's very frustrating, and by example, and most recently with node-red-contrib-ringdoorbell where I've raised an issue, but suspect that the author…

Yes you've raised an issue, you could also offer a Pull Request to fix it. The author may be more responsive to actual offers of help. You can also try a direct email, to check if they are still interested, and then finally yes go ahead and create a new version.

[image] dceejay: You can also try a direct email If you get no luck on their issue list, then this can be a useful next step. One tip - npm owner ls <module-name> will list the owners of the module and their email addresses. Useful if a node doesn't list a git repo or other obvious way to con…

[image] dceejay: You can also try a direct email Tried that. No reply. [image] dceejay: you could also offer a Pull Request to fix it ...and all the other outstanding issues? Future issues? I gave this as an example, and don't get me wrong, there may be good reasons for this: gone ou…

Would it be better to have NR Core members publish the npm module, so the plugin name is owned by NR and more easily transferred to a new maintainer? Maybe a plugin review step, then publish, prior to being displayed for installation. I've had to dive through 4 different AWS SDK plugins repositories…

For those interested, here is a dump of the relevant data. Node-RED Flow Library analysis All... For each node there is column for: when it was first added when it was latest updated how many days since it was created (based on today's date) how many days si…

Is there no way to extract data about 'issues', ie number of, and days since last issue recorded. That maybe would help with the selection criteria.

[image] Paul-Reed: Is there no way to extract data about 'issues', ie number of, and days since last issue recorded. None of that information is held by the flow library - it will be held in what ever issue tracker the node is using. The information can be mined, but is considerable more wor…

Following the discussion for a while I like to add a comment now [image] knolleary: This is one of the reasons we added the ability to rate individual nodes in the flow library - so the community can help curate the list. I’n my personal experience the use of star ratings are very limited. S…

Nick, I've started looking at the nodes from 2014 - how do you want reports? For instance: node-red-contrib-async - a PR was merged 14 days ago, but it doesn't look like it was actually applied to the code. Should I point this out to the owner? Then there is node-red-iced-coffeescript - the contac…

Node-RED

Node-RED Forum

Taking control of contrib nodes when not being maintained

General

Topic		Replies	Views
Paid Nodes Question General	47	2049	21 March 2020
[Article] Node-RED Development: The Numbers General	10	541	3 November 2023
Do you consider it best practice to "keep flows vanilla?" General	25	1666	14 November 2019
Node-RED Survey: Shaping the Future of Node-RED's User Experience News	105	3078	6 October 2025
New Node-RED Editor? Core Development editor	35	776	17 February 2025

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Taking control of contrib nodes when not being maintained

Related topics