@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 14 of 14)
| 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 | |
| 0.10.1 | 5 / 11 | |
| 0.10.0 | 5 / 11 | |
| 0.9.1 | 5 / 11 | |
| 0.9.0 | 5 / 11 | |
| 0.8.2 | 5 / 11 | |
| 0.8.1 | 5 / 9 | |
| 0.8.0 | 5 / 9 |
v0.10.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pythrelease.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.