[FEATURE] adds blockaid scan site service and route

[aristidesstaffieri]

What
Adds Blockaid sdk, service, and route to scan sites

Why
To utilize in our connect dapp flow in order to flag suspicious sites

[stellar-jenkins]

Something went wrong with PR preview build please check

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@blockaid/client@0.11.0	environment, network Transitive: filesystem	+20	13.2 MB	blockaiduser

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
Network access	npm/node-fetch@2.7.0	Module: globalThis["fetch"] Location: Package overview	package.json	🚫
Network access	npm/node-fetch@2.7.0	Module: http Location: Package overview	package.json	🚫
Network access	npm/node-fetch@2.7.0	Module: https Location: Package overview	package.json	🚫
Network access	npm/agentkeepalive@4.5.0	Module: http Location: Package overview	package.json	🚫
Network access	npm/agentkeepalive@4.5.0	Module: https Location: Package overview	package.json	🚫
Network access	npm/@blockaid/client@0.11.0	Module: globalThis["fetch"] Location: Package overview	package.json	🚫

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

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/node-fetch@2.7.0
• @SocketSecurity ignore npm/agentkeepalive@4.5.0
• @SocketSecurity ignore npm/@blockaid/client@0.11.0

[aristidesstaffieri]

I didn't add an explicit loop count to exit this because our fetch client will abort the request after 5 seconds. I was also thinking we may want to handle the misses out of the request lifecycle by making Freighter client poll another route which will check misses separately instead of keeping the request open like this does, thoughts?

[stellar-jenkins]

Preview is available here:
http://freighter-backend-pr99.previews.kube001.services.stellar-ops.com/