@solana/wallet-standard-features
6
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
solana-devs
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate CI/CD migration from solana-devs to GitHub Actions with SLSA provenance; stable for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Solana ecosystem package with 1.1M downloads; dormancy reflects normal release cadence, not takeover. | ai | |
| npm-metadata | no-description | AI (npm-metadata): This is a scoped monorepo package from Solana Foundation; missing description is a cosmetic issue, not a risk indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established Solana Foundation package with clear repo attribution; lack of Sigstore provenance is not a risk for this publisher. | ai | |
| phantom-deps | phantom-dep:@wallet-standard/features | AI (phantom-deps): Declared dep used in config/type declarations rather than direct imports; expected pattern for a feature-definition package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 2 / 1 | |
| 1.3.0 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.0 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 1 |
v1.2.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding
INFO
No provenance attestation
provenance
[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
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.