# 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:** 29

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [16 January 2020 16:16 UTC](https://discourse.nodered.org/t/taking-control-of-contrib-nodes-when-not-being-maintained/20344/29 "2020-01-16T16:16:20Z")

</div>

> [@knolleary](#):
>
> The information can be mined, but is considerable more work than the quick database dump I did this morning.

I think that the best way to enrich the data would be to integrate the [npms.io](http://npms.io) API which already has some metrics about quality.

[https://api-docs.npms.io/](https://api-docs.npms.io/)

This would be better than tracking numbers of stars for sure.

However, it is more work as you say. Shouldn't be hard to do though once you've gone from a one-off db query to a script.

---

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