# Issues with scorecard on flows.nodered.org

**URL:** <https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917>\
**Category:** Developing Nodes\
**Created:** [12 October 2022 08:28 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917 "2022-10-12T08:28:12Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![ptweety](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ptweety/32/68053_2.png) [@ptweety](https://discourse.nodered.org/u/ptweety)\
**Post date:** [12 October 2022 08:28 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/1 "2022-10-12T08:28:12Z")

</div>

Hi all,

I have published a new version of my package [@ptweety/node-red-contrib-ccu](https://github.com/ptweety/node-red-contrib-ccu) and found the following issues with it's [scorecard](https://flows.nodered.org/node/@ptweety/node-red-contrib-ccu/scorecard):

1. Supported Node-RED Version: **Missing**

2. Number of Dependencies: **10**

I also checked my package with

```auto
$ npx node-red-dev validate
    ---Validating Package---
   @ptweety/node-red-contrib-ccu@3.5.2
✅ Package is MIT licensed
✅ Repository/Bugs Link Supplied
✅ Package uses a Scoped Name
✅ Package uses a Scoped Name
✅ No similar named packages found
✅ Node-RED Keyword Found
✅ Compatible with Node-RED v3.0.2
✅ Compatible with Node-RED v1.3.7
✅ Compatible with Node-RED v2.2.3
✅ Compatible NodeJS Version found 14.0.0
    ---Validating Nodes---
    ...
    ---Validating Dependencies---
✅ Package has 5 dependencies
✅ No incompatible packages found in dependency tree
✅ All prod dependencies using latest versions
Complete

```

What can I do to fix this?

Regards  
Matthias

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [12 October 2022 09:29 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/2 "2022-10-12T09:29:04Z")

</div>

Hi @ptweety

checking the logs, you've hit a rare bug we haven't been able to nail down in the flow library.

_Sometimes_ the scorecard reports against an older version of the module than the one that has just been updated. In this screenshot note the `3.5.2` (your latest version) but then the scorecard output reports `3.5.0`.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/7/4770c625f281788ea17865cf2e367c037bb63bde.png)

We haven't been able to figure out what causes this. The code downloads the latest tar file from npm to examine - yet somehow the scorecard 'finds' an old version.

I don't have an immediate workaround for you - we need to get to the bottom of this issue on our side.

---

<div class="post-metadata">

**Author:** ![ptweety](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ptweety/32/68053_2.png) [@ptweety](https://discourse.nodered.org/u/ptweety)\
**Post date:** [12 October 2022 09:40 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/3 "2022-10-12T09:40:25Z")

</div>

Thank you @knolleary,

maybe one additional comment from my side: I was rather quick (max few minutes) to request the update in [flows.nodered.org](http://flows.nodered.org) after I've published to npm.

I can also offer to come back right after I've published the next version, so you can monitor / debug the update process on [flows.nodered.org](http://flows.nodered.org)

---

<div class="post-metadata">

**Author:** ![ptweety](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ptweety/32/68053_2.png) [@ptweety](https://discourse.nodered.org/u/ptweety)\
**Post date:** [29 October 2022 15:41 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/4 "2022-10-29T15:41:13Z")

</div>

Don't know how and when it happened, but now it seems to be fixed.

Thanks!

---

<div class="post-metadata">

**Author:** ![marcboehm](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcboehm/32/70138_2.png) [@marcboehm](https://discourse.nodered.org/u/marcboehm)\
**Post date:** [3 November 2022 11:18 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/5 "2022-11-03T11:18:16Z")

</div>

Hi @knolleary ,

with our package [@captica/node-red-systacomfort2](https://flows.nodered.org/node/@captica/node-red-systacomfort2) we have the same problem. We missed some metadata in the fist version and released a fix pack which passes the node-red-dev validation. But the scorecard still reports the missing attributes.

How can we fix that?

Regards  
Marc

```auto
   ---Validating Package---
   @captica/node-red-systacomfort2@1.0.2
✅ Package is MIT licensed
✅ Repository/Bugs Link Supplied
✅ Package uses a Scoped Name
✅ Package uses a Scoped Name
✅ No similar named packages found
✅ Node-RED Keyword Found
✅ Compatible with Node-RED v3.0.2
 › Warning: P06 NOT Compatible with Node-RED v1.3.7
✅ Compatible with Node-RED v2.2.3
✅ Compatible NodeJS Version found 14.0.0
    ---Validating Nodes---
✅ Nodes all have unique names
✅ Examples found for all nodes
    ---Validating Dependencies---
✅ Package has 0 dependencies
✅ No incompatible packages found in dependency tree
✅ All prod dependencies using latest versions
Complete

```

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [3 November 2022 11:21 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/6 "2022-11-03T11:21:31Z")

</div>

Hi @marcboehm

Thanks for highlighting. As with the previous case, I can see in the logs for some reason the scorecard has re-run against your older version:

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

As I said in my last response:

> [@knolleary](#):
>
> I don't have an immediate workaround for you - we need to get to the bottom of this issue on our side.

I'll try to take a look this week.

---

<div class="post-metadata">

**Author:** ![marcboehm](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcboehm/32/70138_2.png) [@marcboehm](https://discourse.nodered.org/u/marcboehm)\
**Post date:** [3 November 2022 13:43 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/7 "2022-11-03T13:43:56Z")

</div>

Ok, thank you!

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [3 November 2022 14:10 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/8 "2022-11-03T14:10:02Z")

</div>

I think this may be another example of the problem. [[NODE] node-red-contrib-boolean-parser](https://discourse.nodered.org/t/node-node-red-contrib-boolean-parser/69987/)

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [3 November 2022 14:15 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/9 "2022-11-03T14:15:51Z")

</div>

@Colin thanks for linking that.

Looking back in the logs I can confirm it is:

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

Very odd - as the logs show many instances of it working properly. Something curious is going on

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [3 November 2022 15:10 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/10 "2022-11-03T15:10:07Z")

</div>

The current version in npm is 1.2.1 (16 hours ago it says).

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [3 November 2022 15:21 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/11 "2022-11-03T15:21:13Z")

</div>

Could it be to do with two or more releases rapidly one after the other? So another release before the first one has been actioned? Or something like that. I see that has happened to both these nodes.

Though I see not necessarily with @ptweety's node.

---

<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:** [17 November 2022 15:21 UTC](https://discourse.nodered.org/t/issues-with-scorecard-on-flows-nodered-org/68917/12 "2022-11-17T15:21:50Z")

</div>

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