Closed dependabot[bot] closed 11 months ago
socket-security[bot]
commented
11 months ago Updated dependencies detected. Learn more about Socket for GitHub ↗︎
| Packages | Version | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|---|
| @metamask/eth-query | 3.0.1...4.0.0 | None | +0/-0 |
10.8 kB | mcmire |
socket-security[bot]
commented
11 months 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.
| Issue | Package | Version | Note | Source |
|---|---|---|---|---|
| New author | @metamask/eth-query | 4.0.0 |
|
|
| Unstable ownership | @metamask/eth-query | 4.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.
A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.
Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.
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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore @metamask/eth-query@4.0.0
mcmire
commented
11 months ago New author/ownership is okay (I had to manually publish this release due to a glitch)
@SocketSecurity ignore @metamask/eth-query@4.0.0
legobeat
commented
11 months ago @SocketSecurity ignore @metamask/eth-query@4.0.0this bot needs its commands leading *^^
Bumps @metamask/eth-query from 3.0.1 to 4.0.0.
Release notes
Sourced from
@metamask/eth-query's releases.Changelog
Sourced from
@metamask/eth-query's changelog.Commits
3b444724.0.0 (#22)4f1dc24Align types with@metamask/eth-json-rpc-provider(#21)948eabaBump@babel/traversefrom 7.22.8 to 7.23.2 (#20)789ea64Bump postcss from 8.4.25 to 8.4.31 (#19)Maintainer changes
This version was pushed to npm by mcmire, a new releaser for
@metamask/eth-querysince your current version.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