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/update front end #5

Closed
wants to merge 36 commits into from
Closed

Feat/update front end #5

wants to merge 36 commits into from

Conversation

k-g-j
Copy link
Contributor

@k-g-j k-g-j commented Jan 22, 2024

In this PR:

  • Add config for setting custom addresses, urls, etc. . . . per chain for aa methods
  • Addresses bugs found by Matt Walsh
  • Adds to the testing suite
  • Adds userOp methods to front-end (to be removed in subsequent PR)

k-g-j and others added 30 commits January 11, 2024 12:12
…/implement-4337-methods

# Conflicts:
#	packages/snap/package.json
#	packages/snap/src/constants/aa-factories.ts
#	packages/snap/src/constants/chain-ids.ts
#	packages/snap/src/keyring.ts
#	yarn.lock
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
No contributors or author data npm/[email protected]
No contributors or author data npm/@uniswap/[email protected]

View full report↗︎

Next steps

Why is contributor and author data important?

Package does not specify a list of contributors or an author in package.json.

Add a author field or contributors array to package.json.

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

@montelaidev
Copy link
Contributor

Code contained in #4

livingrockrises added a commit to bcnmy/smart-account-keyring-template that referenced this pull request Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants