Aptos CLI

[AlexanderLiteplo]

Looking for feedback on aptos-cli.

[socket-security]

New 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	+52	12.5 MB	aptos-labs
npm/@layerzerolabs/[email protected]	None	+3	1.12 MB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	+1	157 MB	layerzero-bot
npm/@layerzerolabs/[email protected]	Transitive: environment, eval, filesystem, network, unsafe	+141	61 MB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	0	163 kB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	+12	761 kB	layerzero-bot
npm/@layerzerolabs/[email protected]	None	+2	1.04 MB	layerzero-bot
npm/[email protected]	None	0	30.5 kB	benjamn
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell	+30	3.03 MB	anhpnnd, kul, tsjest
npm/[email protected]	None	0	40.6 MB	typescript-bot
npm/[email protected]	environment	0	682 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
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/oft-aptos/package.json pnpm-lock.yaml	⚠︎
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/oft-aptos/package.json pnpm-lock.yaml	⚠︎
Unpopular package	npm/@layerzerolabs/[email protected]	Location: Package overview	examples/oft-aptos/package.json pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

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

[St0rmBr3w]

You guys should heavily consider using this repo as a backboard for your examples.

It already builds with all the repo structures you need:

#1080

[ryandgoulding]

Not to be a nuisance, but can rebase this and squash some commits? 213 commits is a lot for a single PR. Also, need to resolve pnpm-lock.yaml conflicts.