Closed dependabot[bot] closed 7 months ago
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
Package | New capabilities | Transitives | Size | Publisher |
---|---|---|---|---|
npm/@metamask/snaps-controllers@5.0.1 | Transitive: environment, filesystem, network, shell, unsafe | +192 |
42 MB | brad.decker, danfinlay, gudahtt, ...9 more |
🚮 Removed packages: npm/@metamask/snaps-controllers@4.1.0
🚨 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 |
---|---|---|---|
New author | npm/@metamask/post-message-stream@8.0.0 |
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 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/post-message-stream@8.0.0
Looks like @metamask/snaps-controllers is up-to-date now, so this is no longer needed.
Bumps @metamask/snaps-controllers from 4.1.0 to 5.0.1.
Release notes
Sourced from
@metamask/snaps-controllers
's releases.Commits
7f1bdd6
Release 33.0.0 (#2197)f3889b6
Fix issue installing non-allowlisted Snaps in allowlist mode (#2196)c644259
Removeip
npm package (#2184)1b97212
Support new lines in CLI message formatting (#2194)98caeb4
Release 32.0.0 (#2191)1a512f2
Make Webpack plugins add compilation warnings instead of logging (#2192)a783ef6
Add a manifest warning when no icon is found and when icon is not 1:1 (#2185)f201649
Add interactive UI example Snap (#2171)a7b2fe6
Remove icons from package.json (#2190)3feaa15
Delete example snap icons (#2189)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