Merge v12.3.0 into v12.4.0 #27362
Merge v12.3.0 into v12.4.0 #27362
Pull Request #27362 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #27362 Alerts | Found 24 project alerts |
Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.
Details
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
| Alert | Package | Note | Source | CI |
|---|---|---|---|---|
| New author | npm/[email protected] | 🚫 | ||
| Native code | npm/[email protected] |
| 🚫 | |
| Network access | npm/@metamask/[email protected] |
| 🚫 | |
| Network access | npm/@metamask/[email protected] |
| 🚫 | |
| Network access | npm/@metamask/[email protected] |
| 🚫 | |
| Network access | npm/@metamask/[email protected] |
| 🚫 | |
| Network access | npm/[email protected] |
| 🚫 | |
| Network access | npm/[email protected] |
| 🚫 | |
| Network access | npm/[email protected] |
| 🚫 |
Next steps
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.
What's wrong with native code?
Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.
Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.
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.
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 ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/@metamask/[email protected]@SocketSecurity ignore npm/@metamask/[email protected]@SocketSecurity ignore npm/@metamask/[email protected]@SocketSecurity ignore npm/@metamask/[email protected]@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]