@solana-mobile/mobile-wallet-adapter-protocol
An implementation of the Solana Mobile Mobile Wallet Adapter protocol. Use this to open a session with a mobile wallet app, and to issue API calls to it.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@solana/wallet-standard-util | AI (dependencies): Part of the official Solana wallet-standard ecosystem; consistent with other @solana/* deps in this package. Legitimate dependency for this Solana Mobile package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.2.8 | 5 / 5 | |
| 2.2.7 | 5 / 5 | |
| 2.2.6 | 5 / 5 | |
| 2.2.5 | 5 / 5 | |
| 2.2.4 | 4 / 5 | |
| 2.2.3 | 4 / 5 | |
| 2.2.2 | 4 / 5 | |
| 2.2.1 | 4 / 5 | |
| 2.2.0 | 4 / 5 |
v2.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.