# Node catalog purge

**URL:** <https://discourse.nodered.org/t/node-catalog-purge/92831>\
**Category:** General\
**Created:** [31 October 2024 13:22 UTC](https://discourse.nodered.org/t/node-catalog-purge/92831 "2024-10-31T13:22:36Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [31 October 2024 15:46 UTC](https://discourse.nodered.org/t/node-catalog-purge/92831/10 "2024-10-31T15:46:11Z")

</div>

The rate system: if a node has only one vote 5, sorting by "rating" indicates that this node has more weight/highlighted than a node with more votes (e.g. 10 \* 5 and 1 \* 4)

Improve scorecard with a real package evaluation.

> [@FR: Catalog: Limit developer frustration about sorting packages](https://discourse.nodered.org/t/fr-catalog-limit-developer-frustration-about-sorting-packages/83431):
>
> Hi Team, I am one of those developers who took over an existing package because the maintainer no longer cares about his package in order to update it, correct it, make improvements, etc. My biggest frustration (and probably those of other developers) is that my package (being scoped) is not at the top of the list which limits the use of my package. This is also the case for similar names. Below is a related discussion: If I put myself in the end user's shoes, he doesn't want to go through …

---

_[View the full topic](https://discourse.nodered.org/t/node-catalog-purge/92831)._
