Skip to content
This repository has been archived by the owner on Sep 20, 2021. It is now read-only.

[Snyk] Security upgrade sails-hook-sockets from 2.0.0 to 2.0.1 #240

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

merge advice

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-JS-WS-1296835
No No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: sails-hook-sockets The new version differs by 11 commits.
  • 6a3750e 2.0.1
  • 9b56494 Update package.json
  • 41cae9e Revert "updated node version in appveyor config"
  • 7e84ce3 updated node version in appveyor config
  • aeefeae updated node versions in Travis CI config
  • fae468c Update package.json
  • 4d09ed2 Update package.json
  • 561cac3 Update package.json
  • 4eff89a Revert "Revert "Update package.json""
  • a2f6620 Revert "Update package.json"
  • 1d842dd Update package.json

See the full diff

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

@snyk-bot snyk-bot requested a review from a team as a code owner May 26, 2021 21:31
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant