# Taking control of contrib nodes when not being maintained

**URL:** <https://discourse.nodered.org/t/taking-control-of-contrib-nodes-when-not-being-maintained/20344>\
**Category:** General\
**Created:** [14 January 2020 22:24 UTC](https://discourse.nodered.org/t/taking-control-of-contrib-nodes-when-not-being-maintained/20344 "2020-01-14T22:24:41Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [16 January 2020 13:14 UTC](https://discourse.nodered.org/t/taking-control-of-contrib-nodes-when-not-being-maintained/20344/27 "2020-01-16T13:14:47Z")

</div>

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 contact info references a URL that no longer exists.

---

_[View the full topic](https://discourse.nodered.org/t/taking-control-of-contrib-nodes-when-not-being-maintained/20344)._