fix: compatability with metamask app

[Jwhiles]

Description

Uses a custom auth provider in order to allow faucet to connect to mobile apps.

Additionally this makes some UI changes, to avoid showing misleading CTAs when the mobile app is detected.

Checklist

Complete this checklist before merging your PR:

• If this PR contains a major change to the documentation content, I have added an entry to the top of the "What's new?" page.
• The proposed changes have been reviewed and approved by a member of the documentation team.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
metamask-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 27, 2025 9:57am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@metamask/profile-sync-controller@4.1.1 🔁 npm/@metamask/profile-sync-controller@4.1.0	Transitive: environment, eval, filesystem, shell, unsafe	+281	66.3 MB	danfinlay, gudahtt, kumavis, ...6 more

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
High CVE	npm/http-proxy-middleware@2.0.6	CVE: GHSA-c7qv-q95q-8v27 Denial of service in http-proxy-middleware (HIGH) Affected versions: < 2.0.7 Patched version: 2.0.7	package-lock.json package.json	🚫
High CVE	npm/mermaid@10.9.1	CVE: GHSA-m4gq-x24j-jpmf Prototype pollution vulnerability found in Mermaid's bundled version of DOMPurify (HIGH) Affected versions: <= 10.9.2 Patched version: 10.9.3	package-lock.json package.json	🚫
Low CVE	npm/elliptic@6.5.7	CVE: GHSA-fc9h-whq2-v747 Valid ECDSA signatures erroneously rejected in Elliptic (LOW) Affected versions: < 6.6.0 Patched version: 6.6.0	package-lock.json package.json	⚠︎
Medium CVE	npm/path-to-regexp@0.1.10	CVE: GHSA-rhx6-c78j-4q9w Unpatched path-to-regexp ReDoS in 0.1.x (MODERATE) Affected versions: < 0.1.12 Patched version: 0.1.12	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a mild CVE?

Contains a low severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known low severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a medium CVE?

Contains a medium severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known medium severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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/http-proxy-middleware@2.0.6
• @SocketSecurity ignore npm/mermaid@10.9.1
• @SocketSecurity ignore npm/elliptic@6.5.7
• @SocketSecurity ignore npm/path-to-regexp@0.1.10

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.