@fluentui/set-version
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 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.2.24 | 1 / 2 | |
| 8.2.23 | 1 / 2 | |
| 8.2.22 | 1 / 2 | |
| 8.2.21 | 1 / 2 | |
| 8.2.20 | 1 / 2 | |
| 8.2.19 | 1 / 2 | |
| 8.2.18 | 1 / 2 |
v8.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.