@credenza3/core-web-sui-ext
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 |
|---|---|---|
| 0.0.13 | 2 / 4 | |
| 0.0.12 | 1 / 4 | |
| 0.0.11 | 1 / 4 | |
| 0.0.10 | 1 / 4 | |
| 0.0.9 | 1 / 4 | |
| 0.0.8 | 1 / 4 | |
| 0.0.7 | 1 / 4 | |
| 0.0.6 | 1 / 4 |
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.