Closed dependabot[bot] closed 1 month ago
socket-security[bot]
commented
4 months ago New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
| Package | New capabilities | Transitives | Size | Publisher |
|---|---|---|---|---|
| npm/@metamask/safe-event-emitter@3.1.1 | None | 0 |
24.1 kB | lgbot |
🚮 Removed packages: npm/@metamask/safe-event-emitter@3.0.0
socket-security[bot]
commented
4 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.
| Alert | Package | Note | Source |
|---|---|---|---|
| New author | npm/@metamask/safe-event-emitter@3.1.1 | ||
| New author | npm/@metamask/safe-event-emitter@3.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/safe-event-emitter@3.1.1@SocketSecurity ignore npm/@metamask/safe-event-emitter@3.0.0
legobeat
commented
2 months ago @dependabot rebase
legobeat
commented
1 month ago @dependabot recreate
legobeat
commented
1 month ago Folded into #247
dependabot[bot]
commented
1 month ago OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
Bumps @metamask/safe-event-emitter from 3.0.0 to 3.1.1.
Release notes
Sourced from
@metamask/safe-event-emitter's releases.Changelog
Sourced from
@metamask/safe-event-emitter's changelog.Commits
56ac561Release 3.1.1 (#148)5facba9ci: run build/lint/test on nodejs v18, v20; ubuntu-latest (#147)147e95bFix ESM build issues with TSC (#146)b36a4d0fix esm path on package.json (#143)a68ac06Release 3.1.0 (#142)95276c8Add ESM build (#141)d3f56aaEnabling MetaMask security code scanner (#140)d7265afBump@babel/traversefrom 7.8.3 to 7.23.2 (#139)c87f6afBump word-wrap from 1.2.3 to 1.2.4 (#138)63bcf09Bump semver from 5.7.1 to 5.7.2 (#136)Maintainer changes
This version was pushed to npm by lgbot, a new releaser for
@metamask/safe-event-emittersince your current version.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