@zywave/zui-expander
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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 2 / 0 | |
| 4.2.3 | 2 / 0 | |
| 4.2.2 | 2 / 0 | |
| 4.2.1 | 2 / 0 | |
| 4.2.0 | 2 / 0 | |
| 4.1.38 | 2 / 0 | |
| 4.1.37 | 2 / 0 | |
| 4.1.36 | 2 / 0 |
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.