MetaMask
Upgrade allow-scripts; add preinstall-always-fail
This commit aligns this repo with the module template:
- Bump
@lavamoat/allow-scriptsto ^2.3.1 - Add
@lavamoat/preinstall-always-fail, as it was being configured in the manifest, but not actually installed
Removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: @lavamoat/[email protected]
![socket-security[bot] avatar](https://avatars.githubusercontent.com/in/156372?v=4 "Published by a pub.dev verified publisher"){kind=small}
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
| Issue | Package | Version | Note | Source |
|---|---|---|---|---|
| Install scripts | @lavamoat/aa | 3.1.5 |
|
|
| New author | @lavamoat/aa | 3.1.5 | ||
| New author | hasown | 2.0.0 |
|
|
| New author | node-gyp | 9.4.1 |
|
|
| New author | nopt | 6.0.0 |
Next steps
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 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.
Take a deeper look at the dependency
Take 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 package
If 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 risk
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore @lavamoat/[email protected]
Socket errors are okay. We own the @lavamoat/* packages, and ljharb, lukekarrys, and gar are trusted authors.