zwave-js-ui
zwave-js-ui copied to clipboard
[Snyk] Security upgrade axios from 1.6.2 to 1.6.4
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.
Changes included in this PR
- Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
- package.json
Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/
directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn
to update the contents of the ./yarn/cache
directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.
Vulnerabilities that will be fixed
With an upgrade:
Severity | Priority Score (*) | Issue | Breaking Change | Exploit Maturity |
---|---|---|---|---|
661/1000 Why? Recently disclosed, Has a fix available, CVSS 7.5 |
Prototype Pollution SNYK-JS-AXIOS-6144788 |
No | No Known Exploit |
(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information: 🧐 View latest project report
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
💡 The pull request title does not match our guidelines 💡
We follow conventional commits, check out the description and examples. This means that the PR title must...
- start with the type of change, e.g.
feat:
, orfix:
- optionally specify a scope, for example we use
config
for changes to config files:feat(config):
- contain a description that explains what is being changed, e.g. add a parameter, correct a typo, ...
- and ideally explains what the change affects, e.g. the device (manufacturer, device label, firmware, ...)
The description should use uppercase and lowercase normally, except for the first character which must be lowercase.
@chrisns still missing package-lock update
This pull-request is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this pull-request entirely you can add the no-stale label
This pull-request is now closed due to inactivity, you can of course reopen or reference this pull-request if you see fit.