github-actions[bot]
commented
2 weeks ago CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.
Closed cortisiko closed 2 weeks ago
github-actions[bot]
commented
2 weeks ago CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.
socket-security[bot]
commented
2 weeks ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/@metamask/controllers@26.0.0 | network Transitive: filesystem, shell | +59 |
17 MB | rekmarks |
| npm/@metamask/key-tree@9.0.0 | None | +5 |
954 kB | metamaskbot |
| npm/@metamask/post-message-stream@8.0.0 | None | 0 |
71 kB | lgbot |
| npm/@metamask/scure-bip39@2.1.0 | None | +1 |
454 kB | metamaskbot |
| npm/@metamask/snaps-controllers@8.4.0 | Transitive: environment | +10 |
2 MB | metamaskbot |
| npm/@metamask/snaps-rpc-methods@9.1.3 | Transitive: filesystem, network | +16 |
4.52 MB | |
| npm/@metamask/snaps-sdk@4.4.2 | network | +7 |
2.19 MB | metamaskbot |
| npm/@metamask/snaps-utils@7.6.0 | Transitive: filesystem | +18 |
7.44 MB | |
| npm/bip39@2.6.0 | None | 0 |
233 kB | junderw |
| npm/braces@3.0.2 | None | +3 |
98.1 kB | doowb |
| npm/whatwg-fetch@3.6.2 | network | 0 |
54.8 kB | jakechampion |
🚮 Removed packages: npm/@metamask/snaps-controllers@8.3.1, npm/@metamask/snaps-rpc-methods@9.1.2, npm/@metamask/snaps-sdk@4.4.1, npm/@metamask/snaps-utils@7.4.1, npm/braces@3.0.3, npm/web3-core@4.4.0, npm/web3-types@1.6.0, npm/whatwg-fetch@3.6.20, npm/zod@3.23.8
socket-security[bot]
commented
2 weeks ago 🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎
To accept the risk, merge this PR and you will not be notified again.
This module accesses the network.
Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.
This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.
The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.
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.
Contains a dependency which resolves to a remote git URL. Dependencies fetched from git URLs are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.
Publish the git dependency to npm or a private package repository and consume it from there.
Contains a low severity Common Vulnerability and Exposure (CVE).
Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
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.
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.
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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/xhr2-cookies@1.1.0@SocketSecurity ignore npm/xmlhttprequest@1.8.0@SocketSecurity ignore npm/@metamask/types@1.1.0@SocketSecurity ignore npm/bip39@2.6.0@SocketSecurity ignore npm/@metamask/controllers@26.0.0@SocketSecurity ignore npm/web3@0.20.7@SocketSecurity ignore npm/eth-keyring-controller@6.2.1@SocketSecurity ignore npm/eth-hd-keyring@3.6.0@SocketSecurity ignore npm/eth-simple-keyring@4.2.0@SocketSecurity ignore npm/@metamask/post-message-stream@8.0.0
Description
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist