Bump to Yarn v4

[mcmire]

Upgrading to v4 allows us to bring over more things from the module template, such as JavaScript constraints.

4.7.0 is the latest version at the time of this writing.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@isaacs/[email protected]	filesystem	0	101 kB	isaacs
npm/@npmcli/[email protected]	environment, network	+5	290 kB	npm-cli-ops
npm/[email protected]	None	0	177 kB	beaugunderson
npm/[email protected]	None	0	46.9 kB	andyperlitch
npm/[email protected]	None	0	36.5 kB	isaacs
npm/[email protected]	None	0	12.3 kB	npm-cli-ops
npm/[email protected]	None	0	39.9 kB	alexei

View full report↗︎

[socket-security]

👍 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/[email protected], npm/@npmcli/[email protected], npm/[email protected], npm/[email protected], npm/@npmcli/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

[mcmire]

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/@npmcli/[email protected]
@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/@npmcli/[email protected]
@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]

Network access makes sense, Yarn is a CLI that requires an internet connection.

New authors are OK, I have confirmed their legitimacy.