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

revert: feat(swaps): enable Base for swaps (#9286) #9612

Merged
merged 1 commit into from
May 10, 2024

Conversation

chrisleewilcox
Copy link
Contributor

This reverts commit 302d3a4.

Description

Related issues

Reverts: #9286

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • I've completed the PR template to the best of my ability
  • I’ve included tests if applicable
  • I’ve documented my code using JSDoc format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@chrisleewilcox chrisleewilcox requested review from a team as code owners May 10, 2024 19:49
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@chrisleewilcox chrisleewilcox changed the title Revert "feat(swaps): enable Base for swaps (#9286)" revert: feat(swaps): enable Base for swaps (#9286) May 10, 2024
Copy link

🚨 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 NoteSource
Network access npm/xhr2-cookies@1.1.0
Network access npm/xhr2-cookies@1.1.0
Network access npm/xmlhttprequest@1.8.0
Shell access npm/xmlhttprequest@1.8.0
Network access npm/xmlhttprequest@1.8.0
Deprecated npm/@metamask/types@1.1.0
  • Reason: @metamask/types has been folded into @metamask/utils and is no longer being maintained. Please use @metamask/utils going forward.
New author npm/bip39@2.6.0
Network access npm/@metamask/controllers@26.0.0
Git dependency npm/web3@0.20.7
Mild CVE npm/web3@0.20.7
Deprecated npm/eth-keyring-controller@6.2.1
  • Reason: Renamed to "@metamask/eth-keyring-controller"
New author npm/eth-hd-keyring@3.6.0
Deprecated npm/eth-simple-keyring@4.2.0
  • Reason: This package has been renamed to "@metamask/eth-simple-keyring"

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is new author?

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.

What are git dependencies?

Contains a dependency which resolves to a remote git URL. Dependencies fetched from git URLs are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.

Publish the git dependency to npm or a private package repository and consume it from there.

What is a mild CVE?

Contains a low severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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

  • @SocketSecurity ignore npm/xhr2-cookies@1.1.0
  • @SocketSecurity ignore npm/xmlhttprequest@1.8.0
  • @SocketSecurity ignore npm/@metamask/types@1.1.0
  • @SocketSecurity ignore npm/bip39@2.6.0
  • @SocketSecurity ignore npm/@metamask/controllers@26.0.0
  • @SocketSecurity ignore npm/web3@0.20.7
  • @SocketSecurity ignore npm/eth-keyring-controller@6.2.1
  • @SocketSecurity ignore npm/eth-hd-keyring@3.6.0
  • @SocketSecurity ignore npm/eth-simple-keyring@4.2.0

Copy link
Member

@cortisiko cortisiko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ ✅ ✅

Copy link
Contributor

github-actions bot commented May 10, 2024

https://bitrise.io/ Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: a9be4e9
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/36753493-3940-442c-a305-5c09a493b0d2

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Copy link

sonarcloud bot commented May 10, 2024

Quality Gate Passed Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@chrisleewilcox chrisleewilcox merged commit d1393ca into main May 10, 2024
39 of 42 checks passed
@chrisleewilcox chrisleewilcox deleted the swaps/revert-9286 branch May 10, 2024 21:33
@github-actions github-actions bot locked and limited conversation to collaborators May 10, 2024
@metamaskbot metamaskbot added the release-7.24.0 Issue or pull request that will be included in release 7.24.0 label May 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-7.24.0 Issue or pull request that will be included in release 7.24.0 Run Smoke E2E Triggers smoke e2e on Bitrise team-mobile-platform team-swaps
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants