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

Use JSX #211

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Use JSX #211

wants to merge 6 commits into from

Conversation

FrederikBolding
Copy link
Member

Bumps the snaps packages to latest to support JSX and changes the template snap to leverage this new functionality.

Copy link

socket-security bot commented May 14, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/approval-controller@7.0.0 None +1 515 kB metamaskbot
npm/@metamask/controller-utils@11.0.0 network Transitive: filesystem +16 3.25 MB metamaskbot
npm/@metamask/eth-block-tracker@9.0.3 None +2 149 kB lgbot
npm/@metamask/eth-json-rpc-middleware@12.1.2 network +9 896 kB metamaskbot
npm/@metamask/json-rpc-engine@8.0.2 None 0 189 kB metamaskbot
npm/@metamask/permission-controller@10.0.0 None +3 1.08 MB metamaskbot
npm/@metamask/phishing-controller@10.0.0 network +4 1.3 MB metamaskbot
npm/@metamask/post-message-stream@8.1.0 None 0 76 kB lgbot
npm/@metamask/providers@16.1.0 None +3 402 kB metamaskbot
npm/@metamask/snaps-cli@6.2.1 filesystem, network, unsafe Transitive: environment, eval, shell +100 867 MB metamaskbot
npm/@metamask/snaps-controllers@9.2.0 Transitive: environment, filesystem +12 3.68 MB metamaskbot
npm/@metamask/snaps-execution-environments@6.5.0 None +4 5.68 MB metamaskbot
npm/@metamask/snaps-jest@8.2.0 filesystem, network Transitive: environment, eval, shell, unsafe +94 18.2 MB metamaskbot
npm/@metamask/snaps-sdk@6.0.0 network +6 1.7 MB metamaskbot
npm/@metamask/snaps-utils@7.7.0 network Transitive: filesystem +12 10.8 MB metamaskbot

🚮 Removed packages: npm/@metamask/approval-controller@6.0.1, npm/@metamask/controller-utils@9.0.2, npm/@metamask/eth-json-rpc-middleware@12.1.0, npm/@metamask/json-rpc-engine@7.3.3, npm/@metamask/json-rpc-middleware-stream@6.0.2, npm/@metamask/key-tree@9.0.0, npm/@metamask/permission-controller@9.0.2, npm/@metamask/phishing-controller@9.0.1, npm/@metamask/post-message-stream@8.0.0, npm/@metamask/providers@16.0.0, npm/@metamask/snaps-cli@6.1.0, npm/@metamask/snaps-controllers@7.0.1, npm/@metamask/snaps-execution-environments@6.0.0, npm/@metamask/snaps-jest@7.0.0, npm/@metamask/snaps-sdk@4.4.2, npm/@metamask/snaps-utils@7.0.4

View full report↗︎

Copy link

socket-security bot commented Jul 2, 2024

👍 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/@spruceid/siwe-parser@2.1.0

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

@FrederikBolding
Copy link
Member Author

@SocketSecurity ignore npm/@spruceid/siwe-parser@2.1.0

Trusted contributor.

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.

None yet

1 participant