# NPM Maintenance score gone rogue (or maybe not)

**URL:** <https://discourse.nodered.org/t/npm-maintenance-score-gone-rogue-or-maybe-not/62357>\
**Category:** General\
**Created:** [8 May 2022 07:33 UTC](https://discourse.nodered.org/t/npm-maintenance-score-gone-rogue-or-maybe-not/62357 "2022-05-08T07:33:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [8 May 2022 07:33 UTC](https://discourse.nodered.org/t/npm-maintenance-score-gone-rogue-or-maybe-not/62357/1 "2022-05-08T07:33:27Z")

</div>

I noticed this morning my maintenance score went down from 100% to 83%  
That can't be right I thought!

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/2/725d4b02434fb24d7ea67fdf8a2a6490dae7fa0d.png)

Decided to visit NPMjs and found that every package is set to 33%

Seems something has changed or not gone to plan!  
if your like me, and pay attention to your stats, it might be NPM that is at fault maybe

??

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/a/0ae4f373ff72456d0ea861247e5c86e638e12f68.png)

EDIT  
On further looking, I use **[npms.io](http://npms.io)** for the badge, and i spent 2-3 months working on an update, so may not actually be at fault - strange how all packages are at 33% however!

---

<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:** [8 May 2022 14:04 UTC](https://discourse.nodered.org/t/npm-maintenance-score-gone-rogue-or-maybe-not/62357/2 "2022-05-08T14:04:43Z")

</div>

Interesting. Looks like someone internal messed up an update.

uibuilder is also showing as 33 but if we look in [npms.io](http://npms.io), we see:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/8/284edd01daa1bec0bde92c13a15c61605053f715.png)

😀

This from npmjs

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/6/d6ddeae70dbc5fc8c64a2b0bd97cb3671a17bd2d.png)

p=11%, q=91%, m=33%

But then the Flows site also penalises uibuilder:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/3/3398aebed57975205fed91c20416d20cf3b30aa6.png)

Because the required node.js version is slightly different to the current node-red requirement, it thinks that 14 is too many dependencies ☹ and there is 1 dependency (execa) that I can't move to the current version because the author decided to try and force everyone to use ECMA modules. 😡

To be honest though, I use a set of markers that I think are more representative of real-world quality:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/6/4640d02ecefdb5314986722c6ce83d18d67130cb.png)

The quality score comes from [packagequality.com](https://packagequality.com/#?package=node-red-contrib-uibuilder). Deepscan & CodeQL are connected via GitHub automatic actions.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [8 May 2022 14:15 UTC](https://discourse.nodered.org/t/npm-maintenance-score-gone-rogue-or-maybe-not/62357/3 "2022-05-08T14:15:01Z")

</div>

I say!

I Might have to use [packagequality.com](http://packagequality.com) - thanks for the tip!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [7 July 2022 14:15 UTC](https://discourse.nodered.org/t/npm-maintenance-score-gone-rogue-or-maybe-not/62357/4 "2022-07-07T14:15:39Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.