Upgrade to Yarn v3 #82
Conversation
| @@ -25,7 +25,6 @@ | |||
| }, | |||
| "author": "Erik Marks <rekmarks@protonmail.com>", | |||
| "license": "ISC", | |||
| "private": false, | |||
There was a problem hiding this comment.
Yarn seems to have made these changes to the manifest automatically (aside from packageManager).
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again. Next stepsWhat is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. What is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. What is network access?This module accesses the network. Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. What is unstable ownership?A new collaborator has begun publishing package versions. Package stability and security risk may be elevated. Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
|
Hmm, I'll see if I can limit the dependencies above from being bumped. |
We use Yarn v3 for our other libraries, so we're following suit here.
mcmire
force-pushed
the
upgrade-to-yarn-v3
branch
from
55166d4
to
5d4bd17
Compare
|
This PR was stale and outdated, so I rebased it. |
|
Merged changes from |
We use Yarn v3 for our other libraries, so we're following suit here.