@crossmint/client-sdk-react-native-ui
React Native SDK for integrating [Crossmint Wallets](https://docs.crossmint.com) into your mobile application. Provides providers, hooks, and built-in UI for wallet creation, signing, and OTP verification.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bs58 | AI (phantom-deps): Used indirectly through @solana/web3.js and internal Crossmint SDKs. | ai | |
| phantom-deps | phantom-dep:@solana/web3.js | AI (phantom-deps): Declared as both dependency and peerDependency; used indirectly through internal SDKs. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Used indirectly through internal Crossmint SDK dependencies. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Used indirectly through @crossmint/client-sdk-base and other internal dependencies. | ai | |
| phantom-deps | phantom-dep:lodash.isequal | AI (phantom-deps): Used indirectly through internal Crossmint SDK dependencies. | ai | |
| phantom-deps | phantom-dep:react-native-webview | AI (phantom-deps): Platform-specific binary; stable pattern for React Native packages. | ai | |
| phantom-deps | phantom-dep:react-native-svg | AI (phantom-deps): Platform-specific binary; stable pattern for React Native packages. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 1.2.8 | 22 / 4 | |
| 1.2.7 | 22 / 4 | |
| 1.2.6 | 22 / 4 | |
| 1.2.5 | 22 / 4 | |
| 1.2.4 | 22 / 4 | |
| 1.2.3 | 22 / 4 | |
| 1.2.2 | 22 / 4 | |
| 1.2.1 | 22 / 4 | |
| 1.2.0 | 22 / 4 | |
| 1.1.14 | 22 / 4 | |
| 1.1.13 | 22 / 4 | |
| 1.1.12 | 22 / 4 | |
| 1.1.11 | 22 / 4 | |
| 1.1.10 | 22 / 4 | |
| 1.1.9 | 22 / 4 | |
| 1.1.8 | 22 / 4 | |
| 1.1.7 | 22 / 4 | |
| 1.1.6 | 22 / 4 | |
| 1.1.5 | 22 / 4 | |
| 1.1.4 | 22 / 4 | |
| 1.1.3 | 22 / 4 | |
| 1.1.2 | 22 / 4 | |
| 1.1.1 | 22 / 4 | |
| 1.1.0 | 22 / 4 | |
| 1.0.4 | 20 / 4 | |
| 1.0.3 | 20 / 4 | |
| 1.0.2 | 15 / 7 | |
| 0.13.34 | 16 / 7 | |
| 0.13.33 | 16 / 7 | |
| 0.13.32 | 16 / 7 | |
| 0.13.30 | 16 / 7 | |
| 0.13.29 | 16 / 7 | |
| 0.13.28 | 16 / 7 | |
| 0.13.27 | 16 / 7 | |
| 0.13.26 | 16 / 7 | |
| 0.13.25 | 16 / 7 | |
| 0.13.24 | 16 / 7 | |
| 0.13.23 | 16 / 7 | |
| 0.13.22 | 16 / 7 | |
| 0.13.21 | 16 / 7 | |
| 0.13.20 | 16 / 7 | |
| 0.13.19 | 16 / 6 | |
| 0.13.18 | 16 / 6 | |
| 0.13.17 | 16 / 6 | |
| 0.13.16 | 16 / 6 | |
| 0.13.15 | 16 / 6 | |
| 0.13.14 | 14 / 6 | |
| 0.13.13 | 15 / 6 | |
| 0.13.12 | 15 / 6 | |
| 0.13.11 | 15 / 6 | |
| 0.13.10 | 15 / 6 |
v1.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.