Closed dependabot[bot] closed 2 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
Package | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|
npm/@metamask/controller-utils@10.0.0 | network | 0 |
223 kB | metamaskbot |
npm/@metamask/phishing-controller@9.0.4 | network | 0 |
166 kB | metamaskbot |
npm/@spruceid/siwe-parser@2.1.0 | None | 0 |
36.3 kB | sbihel |
npm/valid-url@1.0.9 | None | 0 |
17.2 kB | odysseas |
🚮 Removed packages: npm/@metamask/controller-utils@9.0.2, npm/@metamask/phishing-controller@9.0.1, npm/@spruceid/siwe-parser@1.1.3
🚨 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 |
---|---|---|
New author | npm/@spruceid/siwe-parser@2.1.0 | |
Network access | npm/@metamask/controller-utils@9.1.0 |
|
Network access | npm/@metamask/controller-utils@10.0.0 |
|
Network access | npm/@metamask/phishing-controller@9.0.4 |
|
Network access | npm/@metamask/phishing-controller@9.0.1 |
|
Network access | npm/@metamask/controller-utils@9.0.2 |
|
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.
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 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/@spruceid/siwe-parser@2.1.0
@SocketSecurity ignore npm/@metamask/controller-utils@9.1.0
@SocketSecurity ignore npm/@metamask/controller-utils@10.0.0
@SocketSecurity ignore npm/@metamask/phishing-controller@9.0.4
@SocketSecurity ignore npm/@metamask/phishing-controller@9.0.1
@SocketSecurity ignore npm/@metamask/controller-utils@9.0.2
Superseded by #251.
Bumps @metamask/phishing-controller from 9.0.1 to 9.0.4.
Commits
a137dd1
Release 158.0.0 (#4351)3855767
Revert "Release 158.0.0 (#4342)" (#4350)c2e6752
Release 158.0.0 (#4342)26d4fe4
exclude fields from token list fetch (#4235)0b3ed43
fix: TransactionController afterSign hook should be allowed to modify the tra...a1297d7
feat: add getSelectedMultichainAccount and listMultichainAccounts (#4330)f2823aa
assets-controllers: Remove AllowedActions, AllowedEvents (#4344)0bd0fa4
deps: async-mutex@^0.2.6->^0.5.0 (#4335)e6ecd95
Fully removeeth_sign
(#4319)50efa9c
feat: migrate NftController to BaseControllerV2 (#4310)You can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show