🗞️ Add composer swap examples

[St0rmBr3w]

No description provided.

[ryandgoulding]

Although this is super cool, there is a lot of custom solidity code. I would recommend this is audited before adding it as an example. Maybe we can combine it with other examples work to save some cycles.

[St0rmBr3w]

Although this is super cool, there is a lot of custom solidity code. I would recommend this is audited before adding it as an example. Maybe we can combine it with other examples work to save some cycles.

Yep, the idea would be to get this audited with any other composer examples we want.

Riley mentioned staking, but this really only applies to native assets so Uniswap is the only example we have at the moment.

Do you have any ideas for improving?

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@layerzerolabs/lz-definitions@3.0.28	None	+1	1.02 MB	layerzero-bot
npm/@layerzerolabs/lz-ton-sdk-v2@3.0.28	Transitive: environment, filesystem	+5	4.08 MB	layerzero-bot
npm/@layerzerolabs/test-devtools-evm-foundry@5.1.0	None	0	1.29 MB	layerzero-bot

🚮 Removed packages: npm/@layerzerolabs/lz-definitions@3.0.27, npm/@layerzerolabs/lz-ton-sdk-v2@3.0.27

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/test-devtools-evm-foundry@5.1.0	Location: Package overview	examples/oft-composer-library/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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@layerzerolabs/test-devtools-evm-foundry@5.1.0