@knime/utils
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 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 4 / 9 | |
| 1.12.1 | 4 / 9 | |
| 1.12.0 | 4 / 9 | |
| 1.11.2 | 4 / 9 | |
| 1.11.1 | 4 / 3 | |
| 1.11.0 | 4 / 3 | |
| 1.10.1 | 4 / 3 | |
| 1.10.0 | 4 / 3 | |
| 1.9.2 | 3 / 3 | |
| 1.9.1 | 3 / 3 | |
| 1.9.0 | 3 / 3 | |
| 1.8.0 | 3 / 3 | |
| 1.7.1 | 4 / 3 | |
| 1.7.0 | 4 / 3 | |
| 1.6.2 | 4 / 3 | |
| 1.6.1 | 4 / 3 | |
| 1.6.0 | 4 / 3 | |
| 1.5.9 | 3 / 3 | |
| 1.5.8 | 3 / 3 | |
| 1.5.7 | 3 / 3 | |
| 1.5.6 | 3 / 3 | |
| 1.5.5 | 3 / 3 | |
| 1.5.4 | 3 / 3 | |
| 1.5.3 | 3 / 3 | |
| 1.5.2 | 3 / 3 | |
| 1.5.1 | 3 / 3 | |
| 1.5.0 | 3 / 3 | |
| 1.4.4 | 3 / 3 | |
| 1.4.3 | 3 / 3 | |
| 1.4.2 | 3 / 3 | |
| 1.4.1 | 3 / 3 | |
| 1.0.0 | 4 / 1 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
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.