@solana-program/memo
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): Legitimate migration from human publisher to GitHub Actions CI/CD with SLSA provenance. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established Solana ecosystem package; dormancy consistent with stable library maintenance cycles. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.11.1 | 0 / 13 | |
| 0.11.0 | 0 / 13 | |
| 0.10.0 | 0 / 13 | |
| 0.9.0 | 0 / 13 | |
| 0.8.0 | 0 / 13 |
v0.11.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-29. 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.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.