Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add live staking data with geo-blocking support #11891

Open
wants to merge 34 commits into
base: main
Choose a base branch
from

refactor: update import path for Theme type in StakingEarnings.styles…

57dc357
Select commit
Loading
Failed to load commit list.
Open

feat: add live staking data with geo-blocking support #11891

refactor: update import path for Theme type in StakingEarnings.styles…
57dc357
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts succeeded Oct 21, 2024 in 1m 16s

Pull Request #11891 Alerts: Success

Report Status Message
PR #11891 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/follow-redirects@1.15.9, npm/form-data@4.0.1, npm/@metamask/stake-sdk@0.2.13

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all