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

[Snyk] Security upgrade danger from 10.0.0 to 10.8.0 #6340

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

twilio-product-security

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 601/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution
SNYK-JS-JSONPOINTER-1577288
No Proof of Concept

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

Commit messages
Package name: danger The new version differs by 250 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


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution

@mergify
Copy link
Contributor

mergify bot commented Oct 26, 2022

This PR touches more than one file and has to be reviewed manually. @rmkubik

@mergify mergify bot added the needs-review label Oct 26, 2022
@mergify
Copy link
Contributor

mergify bot commented Oct 26, 2022

Unfortunately the automatic code review has failed. Please click the details button for more information. If the details reveal a fail in Danger please note that there is currently a known issue (#2046) and @rmkubik will merge your PR manually in the coming days. Sorry for the inconvenience.

@mergify mergify bot added the needs-help label Oct 26, 2022
@stale
Copy link

stale bot commented Jan 7, 2023

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Feel free to open a new pull request to resubmit your contribution. Please make sure your fork is synced before opening the pull request. Thank you for your contributions.

@stale stale bot added the stale label Jan 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants