-
-
Notifications
You must be signed in to change notification settings - Fork 111
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: E2E workflow refactor #887
Conversation
d08c625
to
4d7b61b
Compare
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat 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 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 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 obfuscated code?Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware. Packages should not obfuscate their code. Consider not using packages with obfuscated code Take a deeper look at the dependencyTake 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 packageIf 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 riskTo ignore an alert, reply with a comment starting with
|
* feat: extra logs on socket server for analytics cache * feat: bump version
* feat: extra logs on socket server for analytics cache * fix: connect with potentially receiving response from different method
* feat: extra logs on socket server for analytics cache * fix: connect with potentially receiving response from different method * feat: auto detect deeplink protocol support * feat: remove unnecessary option - let wallet send information * fix: unit tests
* feat: extra logs on socket server for analytics cache * fix: connect with potentially receiving response from different method * feat: auto detect deeplink protocol support * feat: event handling with async protocol * fix: unit tests
* feat: generate new dappId when missing * feat: dappId fallback * feat: improved fallback dappId * feat: dappId optimization * feat: cleanup * feat: update * feat: prevent NA * feat: log level
feat: bump socket server
feat: bump version and prevent empty restriction
* feat: no sdk dappid * feat: bump version * feat: cleanup
* feat: release 94.0.0 * fix: changelogs
…#1065) * fix: improper implementation of handleBatchMethod + more robust tests * fix: lint
* feat: always re-emit display uri event * feat: emit connectWithResponse event
* feat: release 95.0.0 * docs: changelogs
chore: bump .change files
* feat: release 96.0.0 * feat: fix tests
* feat: release 97.0.0 * docs: changelog
Fix fake metamask wallet detection See source of the test: https://github.com/EdouardBougon/wagmi/blob/a5e7927dfcb9b3930409056b50f810ed96ca4ffa/packages/core/src/connectors/injected.ts#L53-L81
* fix: rpc protocol resetting after refresh * feat: multiple sdk improvements * feat: wip * fix: unit tests * fix: unit tests * feat: enable in separate PR for better tracking * feat: cleanup
* fix: rpc protocol resetting after refresh * feat: multiple sdk improvements * feat: wip * fix: unit tests * fix: unit tests * feat: restore deletion
* feat: release 98.0.0 * docs: changelogs * fix: unit tests * feat: cleanup
…n of MM onboard status
Quality Gate passedIssues Measures |
closed for a cleaned branch: #1084