@pythnetwork/price-service-client
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a runtime dep used transitively via isomorphic-ws; not a phantom dep. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Type-only dep for ws; expected to not be directly imported in source. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 7 / 8 | |
| 1.10.0 | 7 / 8 | |
| 1.9.1 | 7 / 10 | |
| 1.9.0 | 7 / 10 | |
| 1.8.2 | 7 / 10 | |
| 1.8.1 | 7 / 10 | |
| 1.8.0 | 7 / 10 | |
| 1.7.0 | 7 / 10 | |
| 1.6.2 | 7 / 10 | |
| 1.6.1 | 7 / 10 | |
| 1.6.0 | 7 / 10 | |
| 1.5.0 | 7 / 10 | |
| 1.4.1 | 7 / 10 | |
| 1.4.0 | 7 / 10 |
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.