do not merge yet

[ryandgoulding]

No description provided.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@aptos-labs/[email protected]	network Transitive: environment, filesystem	+50	12 MB	aptos-labs
npm/@layerzerolabs/[email protected]	None	+1	117 kB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	+1	1.03 MB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	+1	164 MB	layerzero-bot
npm/@layerzerolabs/[email protected]	Transitive: environment, eval, filesystem, network, unsafe	+134	62 MB	layerzero-bot
npm/@layerzerolabs/[email protected] 🔁 npm/@layerzerolabs/[email protected]	None	0	166 kB	layerzero-bot
npm/@layerzerolabs/[email protected] 🔁 npm/@layerzerolabs/[email protected]	Transitive: environment, filesystem	+5	4.84 MB	layerzero-bot
npm/@layerzerolabs/[email protected] 🔁 npm/@layerzerolabs/[email protected]	None	+12	765 kB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	0	27.7 kB	layerzero-bot
npm/@layerzerolabs/[email protected] 🔁 npm/@layerzerolabs/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+217	87.4 MB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	0	1.29 MB	layerzero-bot
npm/@types/[email protected]	None	0	8.22 kB	types
npm/[email protected]	filesystem, unsafe Transitive: environment, eval	+130	21.3 MB	rumpl
npm/[email protected]	environment, filesystem	0	75.8 kB	motdotla
npm/[email protected]	Transitive: environment, filesystem, shell	+37	5.82 MB	sboudrias
npm/[email protected]	None	0	30.5 kB	benjamn
npm/[email protected]	environment, filesystem, unsafe Transitive: eval, network, shell	+30	3.03 MB	kul
npm/[email protected]	None	0	681 kB	eemeli

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
Unstable ownership	npm/[email protected]	Author: npm-cli-ops	packages/devtools-move/package.json pnpm-lock.yaml	⚠︎
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/oapp-aptos-move/package.json examples/oft-adapter-aptos-move/package.json examples/oft-aptos-move/package.json pnpm-lock.yaml	⚠︎
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/oapp-aptos-move/package.json examples/oft-adapter-aptos-move/package.json examples/oft-aptos-move/package.json pnpm-lock.yaml	⚠︎
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/oapp-aptos-move/package.json examples/oft-adapter-aptos-move/package.json examples/oft-aptos-move/package.json pnpm-lock.yaml	⚠︎
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/oapp-aptos-move/package.json examples/oft-adapter-aptos-move/package.json examples/oft-aptos-move/package.json pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What is unstable ownership?

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

Try to reduce the number 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.

What are unpopular packages?

This package is not very popular.

Unpopular packages may have less maintenance and contain other problems.

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/@layerzerolabs/[email protected]
• @SocketSecurity ignore npm/@layerzerolabs/[email protected]
• @SocketSecurity ignore npm/@layerzerolabs/[email protected]
• @SocketSecurity ignore npm/@layerzerolabs/[email protected]