Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

chore: bump runtime deps #471

Merged
merged 1 commit into from
Apr 16, 2024

chore: bump runtime deps

15ca577
Select commit
Loading
Failed to load commit list.
Merged

chore: bump runtime deps #471

chore: bump runtime deps
15ca577
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts succeeded Apr 16, 2024 in 13s

Pull Request #471 Alerts: Success

Report Status Message
PR #471 Alerts No new dependency alerts

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Details

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@metamask/[email protected], npm/@metamask/[email protected], npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

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.

Remove the package

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.

Mark a package as acceptable risk

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/[email protected] or ignore all packages with @SocketSecurity ignore-all