fix(devDeps): @lavamoat/allow-scripts@^2.3.1->^3.0.4

[legobeat]

Explanation

• fix(devDeps): @lavamoat/allow-scripts@^2.3.1->^3.0.4
  • Update to latest

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@babel/[email protected]	None	0	80 kB	nicolo-ribaudo
npm/@expo/[email protected]	environment, filesystem, network, shell, unsafe	+1	3.13 MB	brentvatne
npm/@lavamoat/[email protected]	None	0	19.8 kB	boneskull
npm/@lavamoat/[email protected]	environment Transitive: filesystem, unsafe	+9	225 kB	boneskull
npm/@npmcli/[email protected]	environment, shell	0	12.2 kB	npm-cli-ops
npm/@npmcli/[email protected]	environment Transitive: filesystem	+1	20.2 kB	npm-cli-ops
npm/@testing-library/[email protected]	environment	0	5.39 MB	testing-library-bot
npm/@types/[email protected]	None	0	32.8 kB	types
npm/@types/[email protected]	None	0	23.2 kB	types
npm/@wagmi/[email protected]	None	0	308 kB	jmoxey
npm/[email protected]	filesystem	+4	61.9 kB	npm-cli-ops
npm/[email protected]	environment, eval, filesystem	0	1.2 MB	zloirock
npm/[email protected]	environment, shell	0	1.85 MB	nodejs-foundation
npm/[email protected]	environment, filesystem, shell Transitive: network	+5	306 kB	remy
npm/[email protected]	network	0	24.8 kB	tootallnate
npm/[email protected]	environment, filesystem	0	5.57 MB	adamwathan
npm/[email protected]	filesystem, unsafe	0	46.4 kB	oss-bot
npm/[email protected]	network Transitive: environment	+7	7.67 MB	jmoxey
npm/[email protected]	None	0	9.04 MB	mattiasbuelens

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@eslint-community/[email protected], npm/@expo/[email protected], npm/@expo/[email protected], npm/@jridgewell/[email protected], npm/@lavamoat/[email protected], npm/@metamask/[email protected], npm/@nicolo-ribaudo/[email protected], npm/@pkgr/[email protected], npm/@pmmmwh/[email protected], npm/@react-native-async-storage/[email protected], npm/@rollup/[email protected], npm/@rollup/[email protected], npm/@storybook/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@wagmi/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

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

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

Alert	Package	Note	Source	CI
New author	npm/[email protected]	New Author: npm-cli-ops Previous Author: lukekarrys	packages/examples/react-with-custom-modal/package.json	🚫
Unstable ownership	npm/[email protected]	Author: nodejs-foundation	Source	🚫
New author	npm/[email protected]	New Author: nodejs-foundation Previous Author: lukekarrys	Source	🚫

View full report↗︎

Next steps

What 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 unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

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

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