# Npm audit shows security vulnerabilities

**URL:** https://discourse.nodered.org/t/npm-audit-shows-security-vulnerabilities/61292
**Category:** General
**Created:** [14 April 2022 13:33 UTC](https://discourse.nodered.org/t/npm-audit-shows-security-vulnerabilities/61292 "2022-04-14T13:33:03Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![augjoh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/augjoh/32/26464_2.png) [@augjoh](https://discourse.nodered.org/u/augjoh)
#### Post date: [14 April 2022 13:33 UTC](https://discourse.nodered.org/t/npm-audit-shows-security-vulnerabilities/61292/1 "2022-04-14T13:33:03Z")

</div>

When running `npm audit` the following messages are shown:

```auto
node_modules/async
  fs.notify *
  Depends on vulnerable versions of async
  node_modules/fs.notify
    @node-red/nodes *
    Depends on vulnerable versions of fs.notify
    node_modules/@node-red/nodes
      node-red >=0.20.0-beta.2
      Depends on vulnerable versions of @node-red/nodes
      node_modules/node-red

4 high severity vulnerabilities

```

Is there a possibility to fix this without downgrading node-red?

---

<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: [14 April 2022 19:02 UTC](https://discourse.nodered.org/t/npm-audit-shows-security-vulnerabilities/61292/2 "2022-04-14T19:02:14Z")

</div>

I strongly recommend that you leave well alone unless you really know what you are doing. Broken systems are made of audit "fixes".

New vulnerabilities appear constantly and most of them are minor but the important thing is to recognise that some dependent module upgrades will cause the module that relies on them to break.

It is more important to keep installed modules up-to-date along with your OS. It is more important still that you take precautions to prevent unwanted access to your systems.

> [@augjoh](#):
>
> Is there a possibility to fix this without downgrading node-red?

If you downgrade, you will get more warnings not less.

---

<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: [14 April 2022 19:04 UTC](https://discourse.nodered.org/t/npm-audit-shows-security-vulnerabilities/61292/3 "2022-04-14T19:04:24Z")

</div>

What version of Node-RED are you running this against?

---

<div class="post-metadata">

### Author: ![augjoh](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/augjoh/32/26464_2.png) [@augjoh](https://discourse.nodered.org/u/augjoh)
#### Post date: [15 April 2022 06:00 UTC](https://discourse.nodered.org/t/npm-audit-shows-security-vulnerabilities/61292/4 "2022-04-15T06:00:25Z")

</div>

I'm always using the latest and greatest:

```auto
$ npm ls --production
@platynum/certification-authority@2.1.0 /builds/platynum/certification-authority/flows
[...]
+-- node-red-dashboard@3.1.6
+-- node-red@2.2.2
[...]

```

---

<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: [14 June 2022 06:00 UTC](https://discourse.nodered.org/t/npm-audit-shows-security-vulnerabilities/61292/5 "2022-06-14T06:00:40Z")

</div>

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