@mpen/imut-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 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.5.5 | 1 / 6 | |
| 0.5.4 | 1 / 6 | |
| 0.5.3 | 1 / 6 | |
| 0.5.2 | 0 / 6 | |
| 0.5.1 | 0 / 6 | |
| 0.5.0 | 0 / 6 | |
| 0.4.0 | 0 / 6 | |
| 0.3.1 | 0 / 6 | |
| 0.3.0 | 0 / 6 | |
| 0.2.3 | 0 / 6 | |
| 0.2.2 | 0 / 6 | |
| 0.2.1 | 0 / 6 | |
| 0.2.0 | 0 / 6 | |
| 0.1.53 | 0 / 11 | |
| 0.1.52 | 0 / 11 | |
| 0.1.51 | 0 / 11 | |
| 0.1.50 | 0 / 11 | |
| 0.1.49 | 0 / 11 | |
| 0.1.48 | 0 / 11 | |
| 0.1.47 | 0 / 11 | |
| 0.1.46 | 0 / 11 | |
| 0.1.45 | 0 / 11 | |
| 0.1.44 | 0 / 11 |
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.