@solana/wallet-standard-wallet-adapter-base
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): Transition from solana-devs to GitHub Actions CI/CD with SLSA provenance; legitimate CI migration. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Solana package resuming publishes via CI; dormancy is normal for stable libs. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package from the official Solana Foundation; missing description is a cosmetic gap, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established Solana Foundation package predating widespread provenance adoption; absence is not a risk signal for this publisher. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.1.5 | 8 / 3 | |
| 1.1.4 | 8 / 3 | |
| 1.1.3 | 8 / 3 | |
| 1.1.2 | 8 / 4 | |
| 1.1.1 | 8 / 4 | |
| 1.1.0 | 8 / 4 | |
| 1.0.2 | 8 / 4 | |
| 1.0.1 | 8 / 4 | |
| 1.0.0 | 8 / 4 |
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.