Skip to content
This repository has been archived by the owner on Oct 7, 2024. It is now read-only.

16.0.0 #304

Merged
merged 9 commits into from
Jan 12, 2024
Merged

16.0.0 #304

merged 9 commits into from
Jan 12, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Nov 22, 2023

Copy link

socket-security bot commented Nov 22, 2023

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

Packages Version New capabilities Transitives Size Publisher
@metamask/keyring-api 2.0.0 network +93 26 MB metamaskbot

🚮 Removed packages: @metamask/eth-keyring-controller@15.1.0

@legobeat legobeat marked this pull request as ready for review November 23, 2023 06:52
@legobeat legobeat requested a review from a team as a code owner November 23, 2023 06:52
@legobeat legobeat requested review from FrederikBolding and a team November 23, 2023 06:53
@mikesposito mikesposito mentioned this pull request Nov 23, 2023
NicholasEllul
NicholasEllul previously approved these changes Nov 29, 2023
* Prefer cached `encryptionKey` for encryption when possible (#307)

* fix: prefer encryptionKey for encryption when possible

* refactor: add test case

* Use encryptor `isVaultUpdated` (#310)

* chore: update browser-passworder

* refactor: remove `updateVault` from `GenericEncryptor`
Copy link
Member

@Gudahtt Gudahtt left a comment

Choose a reason for hiding this comment

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

This requires an update now that #310 is merged

github-actions bot and others added 2 commits November 29, 2023 19:16
* 15.1.0

* edit changelog entries

* rephrase changelog entry

---------

Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Michele Esposito <michele@esposito.codes>
* origin/main:
  Use encryptor `isVaultUpdated` (#310)
  Bump @metamask/browser-passworder from 4.2.0 to 4.3.0 (#311)
  Prefer cached `encryptionKey` for encryption when possible (#307)
  Bump @metamask/obs-store from 8.1.0 to 9.0.0 (#306)
  Bump @metamask/eth-sig-util from 7.0.0 to 7.0.1 (#302)
@legobeat
Copy link
Contributor

legobeat commented Nov 29, 2023

This requires an update now that #310 is merged

Might as well get in #314 as well before merging this.

UPDATE: Rebased on top of #314

Copy link

socket-security bot commented Jan 11, 2024

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue Package Version Note Source
Network access @metamask/snaps-sdk 1.3.2
Network access @metamask/snaps-utils 5.1.2
Shell access @metamask/snaps-utils 5.1.2
No README @spruceid/siwe-parser 1.1.3
Shell access @metamask/snaps-controllers 3.6.0

Ignoring: setimmediate@1.0.5, bs58@4.0.1, ripemd160@2.0.2, validate-npm-package-name@5.0.0, md5.js@1.3.5, @metamask/eth-query@4.0.0, rlp@2.2.7, extension-port-stream@3.0.0, browserify-zlib@0.2.0

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.

Why are READMEs important?

Package does not have a README. This may indicate a failed publish or a low quality package.

Add a README to to the package and publish a new version.

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 package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore @spruceid/siwe-parser@1.1.3
  • @SocketSecurity ignore @metamask/snaps-controllers@3.6.0
  • @SocketSecurity ignore @metamask/snaps-utils@5.1.2
  • @SocketSecurity ignore @metamask/snaps-sdk@1.3.2

@legobeat
Copy link
Contributor

@SocketSecurity ignore setimmediate@1.0.5
@SocketSecurity ignore bs58@4.0.1
@SocketSecurity ignore ripemd160@2.0.2
@SocketSecurity ignore validate-npm-package-name@5.0.0
@SocketSecurity ignore md5.js@1.3.5
@SocketSecurity ignore rlp@2.2.7
@SocketSecurity ignore extension-port-stream@3.0.0
@SocketSecurity ignore browserify-zlib@0.2.0

New authors OK

(It's not clear to me why any of these are being flagged in this PR and not in the most recent merged ones)

@legobeat

This comment was marked as resolved.

@legobeat
Copy link
Contributor

legobeat commented Jan 11, 2024

@SocketSecurity ignore @metamask/eth-query@4.0.0

new author ok

@legobeat legobeat requested a review from a team January 11, 2024 16:32
@legobeat legobeat merged commit af5baf1 into main Jan 12, 2024
18 of 19 checks passed
@legobeat legobeat deleted the release/16.0.0 branch January 12, 2024 18:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants