@solana-mobile/mobile-wallet-adapter-protocol-web3js
A convenience wrapper that enables you to call Solana Mobile Stack protocol methods using objects from @solana/web3.js
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of the official Solana Mobile monorepo; sparse README and missing keywords are cosmetic issues common in SDK sub-packages, not spam indicators. | ai | |
| dependencies | unvetted-dep:@solana-mobile/mobile-wallet-adapter-protocol | AI (dependencies): Sibling package from the same official Solana Mobile monorepo; a natural and expected dependency for this wrapper package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.2.8 | 3 / 4 | |
| 2.2.7 | 3 / 4 | |
| 2.2.6 | 3 / 4 | |
| 2.2.5 | 3 / 4 | |
| 2.2.4 | 3 / 4 | |
| 2.2.3 | 3 / 4 | |
| 2.2.2 | 3 / 4 | |
| 2.2.0 | 3 / 4 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.