@solana/wallet-standard
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI/CD publish with SLSA attestation; legitimate transition for this official Solana package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): This is a monorepo aggregator/re-export package from the official Solana ecosystem; missing description is a cosmetic issue, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established Solana Labs package with 38 versions and 1358-day history; lack of Sigstore provenance is not unusual for this package's age and publish workflow. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.1.5 | 2 / 1 | |
| 1.1.4 | 2 / 1 | |
| 1.1.3 | 2 / 1 | |
| 1.1.2 | 2 / 1 | |
| 1.1.1 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.2 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 |
v1.1.5
2 findingsThis version was published by a different npm account than previous versions on 2026-06-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.