Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade notifications-node-client from 4.8.0 to 4.9.0 #378

Merged
merged 1 commit into from
Aug 21, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to fix one or more vulnerable packages in the `npm` 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
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 619/1000
Why? Has a fix available, CVSS 8.1
Prototype Pollution
SNYK-JS-AJV-584908
No No Known Exploit

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

Commit messages
Package name: notifications-node-client The new version differs by 7 commits.

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

@warrensearle warrensearle merged commit 8b0f09b into master Aug 21, 2020
@warrensearle warrensearle deleted the snyk-fix-61225836625823b819b8dfe39cf2a912 branch August 21, 2020 10:31
warrensearle added a commit that referenced this pull request Mar 21, 2021
…9cf2a912

[Snyk] Security upgrade notifications-node-client from 4.8.0 to 4.9.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants