feat: init @ledgerhq/crypto-icons library (provider version)

[mwiercinska]

First iteration of the @ledgerhq/crypto-icons library.
LIVE-11698
LIVE-11701

Can be tested locally with pnpm-link or by running pnpm i && pnpm build && pnpm pack and then pointing to the package location in a consumer's package.json e.g.
"@ledgerhq/crypto-icons": "file:../crypto-icons/lib/ledgerhq-crypto-icons-1.0.0.tgz"

The following will be in follow-up PRs:

• Update COINGECKO_MAPPED_ASSETS_URL to prod url
• Deploying Storybook (+ re-deploy on asset change)
• Build and publish workflow
• Additional testing
• README

[cloudflare-workers-and-pages]

Deploying crypto-icons with    Cloudflare Pages

Latest commit:	6ca74e6
Status:	✅  Deploy successful!
Preview URL:	https://401ad1d0.crypto-icons.pages.dev
Branch Preview URL:	https://live-11698-create-ledgerhq-c.crypto-icons.pages.dev

View logs

[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
Install scripts	npm/[email protected]	Install script: postinstall Source: node -e "try{require('./config/scripts/postinstall')}catch(e){}"	🚫
Install scripts	npm/@swc/[email protected]	Install script: postinstall Source: node postinstall.js	🚫
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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

[beths-ledger]

some interim comments - also covered in slack to make back and forth a bit easier!

[sarneijim]

LGTM!

[KVNLS]

Great job! I think that we can improve few details.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, network	+5	2.42 MB	jasonsaayman
npm/[email protected]	environment, filesystem, unsafe	0	7.7 MB	prettier-bot
npm/[email protected]	None	0	21.9 MB	typescript-bot

View full report↗︎