Closed dependabot[bot] closed 4 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
Package | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|
npm/@metamask/json-rpc-middleware-stream@6.0.2 | Transitive: environment, network | +30 |
5 MB | metamaskbot |
npm/@metamask/providers@15.0.0 | Transitive: environment, network | +39 |
5.63 MB | metamaskbot |
npm/@metamask/snaps-sdk@3.1.1 | network Transitive: environment | +47 |
7.91 MB | metamaskbot |
npm/@types/uuid@9.0.7 | None | 0 |
6.65 kB | types |
🚮 Removed packages: npm/@metamask/keyring-api@3.0.0, npm/@metamask/providers@14.0.2, npm/@metamask/snaps-sdk@1.4.0, npm/@types/uuid@9.0.8, npm/is-svg@4.4.0, npm/json-rpc-middleware-stream@5.0.1
🚨 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 |
---|---|---|
No contributors or author data | npm/@metamask/snaps-sdk@3.1.1 |
|
Package does not specify a list of contributors or an author in package.json.
Add a author field or contributors array to package.json.
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/@metamask/snaps-sdk@3.1.1
Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase
.
Superseded by #371.
Bumps @metamask/keyring-api from 3.0.0 to 4.0.2.
Release notes
Sourced from
@metamask/keyring-api
's releases.Changelog
Sourced from
@metamask/keyring-api
's changelog.Commits
e174146
4.0.2 (#273)d0eb11a
Bump snaps-sdk version (#271)fc833cb
chore(deps): bump@metamask/safe-event-emitter
from 3.0.0 to 3.1.0 (#270)f65860c
ci: update security code scanner file (#269)2164741
fix: bundler URL validation (#262)a95c7f9
4.0.1 (#268)cb406a0
chore: bump dependencies (#266)9f2720f
chore(deps): bump@metamask/json-rpc-engine
from 7.3.2 to 7.3.3 (#264)db3adae
docs: add note toeth_prepareUserOperation
method response (#263)c7c50e5
chore(deps): bump@metamask/snaps-sdk
from 3.0.0 to 3.0.1 (#261)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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