Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Upgrade merge to version 1.2.1 or later.
See original GitHub issueIt appears you have a downstream dependency on a vulnerable package merge. Please refer to my detailed issue on a a more upstream project. The issue was flagged automatically on my GitHub repository as a “high severity” alert.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
merge@1.2.1 - Snyk Vulnerability Database
Learn more about known merge 1.2.1 vulnerabilities and licenses detected. ... Upgrade merge to version 2.1.1 or higher. <2.1.1.
Read more >Update dependency lookbook to '~> 1.2', '>= 1.2.1' (!99759) · Merge ...
This MR contains the following updates: Package Update Change lookbook minor. ... This Merge Request has been created with the help of renovate-gitlab-bot ......
Read more >merge | npm | Open Source Insights
Merge multiple objects into one, optionally creating a new cloned object. Similar to the jQuery.extend but more flexible. Works in Node.js and the...
Read more >QID 983156: Nodejs (npm) Security Update for merge (GHSA ...
The `merge. recursive` function can be tricked into adding or modifying properties of the Object prototype. Update to version 1.2. 1 or later....
Read more >Compose UI - Android Developers
Latest Update, Stable Release, Release Candidate, Beta Release ... androidx.compose.ui:ui-*:1.2.1 is released. Version 1.2.1 contains these commits.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can confirm that deleting package-lock.json and node_modules and then running npm install works to upgrade merge to 1.2.1.
@forgo try deleting your
package-lock.jsonandnode_modulesfolder, then run npm install again.