@hpcc-js/dataflow
hpcc-js - Data Flow
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
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 9.7.6 | 0 / 3 | |
| 9.7.5 | 0 / 3 | |
| 9.7.4 | 0 / 3 | |
| 9.7.3 | 0 / 3 | |
| 9.7.2 | 0 / 3 | |
| 9.7.1 | 0 / 3 | |
| 9.7.0 | 0 / 3 | |
| 9.6.14 | 0 / 3 | |
| 9.6.13 | 0 / 3 | |
| 9.6.12 | 0 / 3 | |
| 9.6.11 | 0 / 3 | |
| 9.6.10 | 0 / 3 | |
| 9.6.9 | 0 / 3 | |
| 9.6.7 | 0 / 3 | |
| 9.6.6 | 0 / 3 | |
| 9.6.5 | 0 / 3 | |
| 9.6.4 | 0 / 3 | |
| 9.6.3 | 0 / 3 | |
| 9.6.2 | 0 / 3 | |
| 9.6.1 | 0 / 3 | |
| 9.6.0 | 0 / 3 | |
| 9.5.1 | 0 / 3 | |
| 9.5.0 | 0 / 3 | |
| 9.4.3 | 0 / 4 | |
| 9.4.2 | 0 / 4 | |
| 9.4.1 | 0 / 4 | |
| 9.4.0 | 0 / 4 | |
| 9.3.9 | 0 / 4 | |
| 9.3.8 | 0 / 4 | |
| 9.3.7 | 0 / 4 | |
| 9.3.6 | 0 / 4 | |
| 9.3.5 | 0 / 4 | |
| 9.3.4 | 0 / 4 | |
| 9.3.3 | 0 / 4 | |
| 9.3.2 | 0 / 4 | |
| 9.3.1 | 0 / 4 | |
| 9.3.0 | 0 / 4 | |
| 9.2.1 | 0 / 4 | |
| 9.2.0 | 0 / 4 | |
| 9.1.0 | 0 / 4 | |
| 9.0.0 | 0 / 4 |
v9.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.