@hpcc-js/wasm-zstd
hpcc-js - WASM zstd
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
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 0 / 2 | |
| 1.14.3 | 0 / 2 | |
| 1.13.5 | 0 / 2 | |
| 1.13.4 | 0 / 2 | |
| 1.13.3 | 0 / 2 | |
| 1.13.2 | 0 / 2 | |
| 1.13.1 | 0 / 2 | |
| 1.13.0 | 0 / 2 | |
| 1.12.6 | 0 / 2 | |
| 1.12.5 | 0 / 2 | |
| 1.12.4 | 0 / 2 | |
| 1.12.2 | 0 / 2 | |
| 1.12.1 | 0 / 2 | |
| 1.12.0 | 0 / 2 | |
| 1.11.1 | 0 / 2 | |
| 1.11.0 | 0 / 2 | |
| 1.10.0 | 0 / 2 | |
| 1.9.1 | 0 / 2 | |
| 1.9.0 | 0 / 2 | |
| 1.8.0 | 0 / 1 | |
| 1.7.0 | 0 / 1 | |
| 1.5.1 | 0 / 1 | |
| 1.5.0 | 0 / 1 | |
| 1.4.0 | 0 / 1 | |
| 1.3.2 | 0 / 1 | |
| 1.3.1 | 0 / 1 | |
| 1.3.0 | 0 / 0 | |
| 1.2.1 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 1 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 1 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.