Shows 3 high severity vulnerabilities when installing npm packages.

[xayanide]

Describe the bug
What isn't working as intended, and what does it affect?
data-store
Affects vulnerability

Affected versions
What versions are affected by this bug? (e.g. >=3.0.1, 2.5.1-2.6.3, >=1.2.0)
3.0.0-next.4^

Steps to reproduce
Steps to reproduce the behavior. (e.g. click on a button, enter a value, etc. and see error)

1. Type and enter npm i in the cli or terminal.

Expected behavior
What is expected to happen?
Show no vulnerability.

Actual behavior
What actually happens? Attach or add errors or screenshots here as well.

Shows 3 severity vulnerabilities that is related to the data-store dependency.

PS C:\Users\Ava\Documents\GitHub\Quaver> npm i

> quaver@3.4.0-next.53 postinstall
> patch-package

patch-package 6.4.7
Applying patches...
@lavaclient/queue@2.0.6 ✔

up to date, audited 195 packages in 6s

21 packages are looking for funding
  run `npm fund` for details

3 high severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

PS C:\Users\Ava\Documents\GitHub\Quaver> npm audit
# npm audit report

node-fetch  <2.6.7
Severity: high
node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor - https://github.com/advisories/GHSA-r683-j2x4-v87g
fix available via `npm audit fix`
node_modules/node-fetch

set-value  3.0.0 - 4.0.0
Severity: high
Prototype Pollution in set-value - https://github.com/advisories/GHSA-4jqc-8m5r-9rpr
fix available via `npm audit fix --force`
Will install data-store@3.1.0, which is a breaking change
node_modules/set-value
  data-store  >=4.0.0
  Depends on vulnerable versions of set-value
  node_modules/data-store

3 high severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

[zapteryx]

jonschlinkert/data-store#43

[github-actions]

🎉 This issue has been resolved in version 4.0.0-next.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀