Revert "Release 14.0.0 (#377)"

[Mrtenz]

This reverts commit 597ecb6.

The release failed because the workflow assumes a build script exists, but we don't build anything in this repo. Will fix this in a separate PR.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@ampproject/[email protected]	None	0	76 kB	jridgewell
npm/@babel/[email protected]	environment	0	24.1 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	101 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment, filesystem, unsafe	0	788 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	487 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	52.3 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	63.7 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	160 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	114 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	14.1 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	31.8 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	49.3 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	11.8 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	928 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment	0	20.3 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	1.89 MB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	68.7 kB	existentialism, hzoo, jlhwung, ...1 more
npm/@babel/[email protected]	None	0	4.13 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	6.86 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	70.4 kB	nicolo-ribaudo
npm/@babel/[email protected]	None	0	731 kB	nicolo-ribaudo
npm/@babel/[email protected]	environment	0	2.48 MB	nicolo-ribaudo
npm/@metamask/[email protected]	None	0	0 B
npm/@metamask/[email protected]	None	0	0 B
npm/@types/[email protected]	None	0	25.7 kB	types
npm/[email protected]	environment, filesystem	0	63 kB	ai
npm/[email protected]	None	0	2.1 MB	ai, beneb, caniuse-lite
npm/[email protected]	None	0	148 kB	kilianvalkhof
npm/[email protected]	None	0	32 kB	mathias
npm/[email protected]	None	0	23.9 kB	voxpelli
npm/[email protected]	None	0	72 kB	isaacs
npm/[email protected]	environment, filesystem, shell	0	14.8 kB	ai

🚮 Removed packages: npm/@types/[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	CI
Deprecated	npm/[email protected]	Reason: Rimraf versions prior to v4 are no longer supported	⚠︎
Deprecated	npm/[email protected]	Reason: This version is no longer supported. Please see https://eslint.org/version-support for other options.	⚠︎

View full report↗︎

Next steps

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

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]