@pythnetwork/pyth-solana-receiver
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 manual 'pythrelease' to GitHub Actions CI/CD publishing, backed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is consistent with legitimate project maintenance patterns for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding VAA/accumulator update data is core oracle SDK functionality, not malicious payload hiding. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of price feed IDs (0x-prefixed) is standard oracle SDK behavior. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 6 / 7 | |
| 0.15.0 | 6 / 7 | |
| 0.14.0 | 6 / 10 | |
| 0.13.0 | 5 / 10 | |
| 0.12.0 | 5 / 12 | |
| 0.11.0 | 5 / 12 | |
| 0.10.2 | 5 / 12 |
v0.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-13. 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.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.