@fluentui/react-window-provider
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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.3.2 | 2 / 5 | |
| 2.3.1 | 2 / 5 | |
| 2.3.0 | 2 / 5 | |
| 2.2.30 | 2 / 5 | |
| 2.2.29 | 2 / 5 | |
| 2.2.28 | 2 / 5 | |
| 2.2.27 | 2 / 5 | |
| 2.2.26 | 2 / 5 | |
| 2.2.25 | 2 / 5 | |
| 2.2.24 | 2 / 5 | |
| 2.2.23 | 2 / 5 | |
| 2.2.22 | 2 / 5 |
v2.2.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.