@solana-mobile/wallet-standard-mobile
A wallet-standard wallet for mobile wallet apps that conform to the Solana Mobile Wallet Adapter protocol
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:tslib | AI (phantom-deps): tslib is a declared runtime dependency used as a TypeScript compilation helper; phantom-dep flag is a stable false positive for TypeScript-compiled packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a legitimate SDK sub-package from the Solana Mobile org; sparse README and missing keywords are cosmetic issues common in monorepo SDK packages, not spam indicators. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.5.2 | 10 / 4 | |
| 0.5.1 | 10 / 4 | |
| 0.5.0 | 10 / 4 | |
| 0.4.4 | 8 / 4 | |
| 0.4.3 | 8 / 4 | |
| 0.4.2 | 8 / 4 | |
| 0.4.1 | 8 / 4 | |
| 0.4.0 | 8 / 4 | |
| 0.3.0 | 8 / 4 | |
| 0.2.0 | 8 / 5 |
v0.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.