Skip to content

chore!: Synchronize package with module template (Nov 2024)#198

Merged
FrederikBolding merged 8 commits intomainfrom
fb/template-sync-nov2024
Nov 26, 2024
Merged

chore!: Synchronize package with module template (Nov 2024)#198
FrederikBolding merged 8 commits intomainfrom
fb/template-sync-nov2024

Conversation

@FrederikBolding
Copy link
Member

@FrederikBolding FrederikBolding commented Nov 25, 2024

Synchronizes the package with the module template to get it up to speed.

  • BREAKING: Updates engines to require at least Node 18
  • Updates to Yarn 4
  • Updates linting configs to latest
  • Bump @metamask/utils to latest
  • Update CI scripts to latest

@socket-security
Copy link

socket-security bot commented Nov 25, 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/mz@2.7.0, npm/abbrev@2.0.0, npm/agent-base@7.1.1, npm/@npmcli/agent@2.2.2, npm/validate-npm-package-name@5.0.1, npm/emoji-regex-xs@1.0.0, npm/node-gyp@10.2.0, npm/@lavamoat/aa@4.3.0, npm/@lavamoat/preinstall-always-fail@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 FrederikBolding changed the title chore!: Synchronise package with module template chore!: Synchronize package with module template (Nov 2024) Nov 25, 2024
@FrederikBolding FrederikBolding force-pushed the fb/template-sync-nov2024 branch from 3df5b83 to 67a28a8 Compare November 25, 2024 13:41
Co-authored-by: Maarten Zuidhoorn <maarten@zuidhoorn.com>
@FrederikBolding
Copy link
Member Author

@SocketSecurity ignore npm/@lavamoat/aa@4.3.0
@SocketSecurity ignore npm/@lavamoat/preinstall-always-fail@2.1.0
This is ours.

@SocketSecurity ignore npm/mz@2.7.0

Used by arethetypeswrong, permissions are expected.

@SocketSecurity ignore npm/abbrev@2.0.0
@SocketSecurity ignore npm/node-gyp@10.2.0
@SocketSecurity ignore npm/validate-npm-package-name@5.0.1
@SocketSecurity ignore npm/agent-base@7.1.1

Trusted author(s).

@SocketSecurity ignore npm/@npmcli/agent@2.2.2

Permissions are expected.

@SocketSecurity ignore npm/emoji-regex-xs@1.0.0

Used by typedoc, doens't look like a typosquat.

@socket-security
Copy link

Report too large to display inline

View full report↗︎

@FrederikBolding FrederikBolding marked this pull request as ready for review November 26, 2024 10:11
@FrederikBolding FrederikBolding requested a review from a team as a code owner November 26, 2024 10:11
@FrederikBolding FrederikBolding merged commit 6dff088 into main Nov 26, 2024
@FrederikBolding FrederikBolding deleted the fb/template-sync-nov2024 branch November 26, 2024 10:11
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