@fluentui/react-utilities
A set of general React-specific utilities.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established Microsoft Fluent UI monorepo package; short README and no keywords are cosmetic issues typical of large internal utility packages, not spam indicators. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party @fluentui org dependency maintained by the same Microsoft team; expected internal dependency for this ecosystem. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui org dependency maintained by the same Microsoft team; expected internal dependency for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@fluentui/keyboard-keys | AI (phantom-deps): Same org scope; phantom detection in large monorepo packages is a common false positive due to re-export patterns. | ai |
Versions (showing 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 9.26.5 | 3 / 0 | |
| 9.26.4 | 3 / 0 | |
| 9.26.3 | 3 / 0 | |
| 9.26.2 | 3 / 0 | |
| 9.26.1 | 3 / 0 | |
| 9.26.0 | 3 / 3 | |
| 9.25.4 | 3 / 3 | |
| 9.25.3 | 3 / 3 | |
| 9.25.2 | 3 / 3 | |
| 9.25.1 | 3 / 3 | |
| 9.25.0 | 3 / 3 | |
| 9.24.1 | 3 / 3 | |
| 9.24.0 | 3 / 3 | |
| 9.23.2 | 3 / 3 | |
| 9.23.1 | 3 / 3 | |
| 9.23.0 | 3 / 3 | |
| 9.22.0 | 3 / 3 | |
| 9.21.1 | 3 / 3 | |
| 9.21.0 | 3 / 3 | |
| 9.20.0 | 3 / 3 | |
| 9.19.0 | 3 / 3 | |
| 9.18.23 | 3 / 3 | |
| 9.18.22 | 3 / 3 | |
| 9.18.21 | 3 / 3 | |
| 9.18.20 | 3 / 3 | |
| 9.18.19 | 3 / 3 | |
| 9.18.18 | 3 / 3 | |
| 9.18.17 | 3 / 3 | |
| 9.18.16 | 3 / 4 | |
| 9.18.15 | 3 / 4 | |
| 9.18.14 | 3 / 3 | |
| 9.18.13 | 3 / 3 | |
| 9.18.12 | 3 / 3 | |
| 9.18.11 | 3 / 3 | |
| 9.18.10 | 3 / 3 | |
| 9.18.9 | 3 / 3 | |
| 9.18.8 | 3 / 3 | |
| 9.18.7 | 3 / 3 | |
| 9.18.6 | 3 / 3 | |
| 9.18.5 | 3 / 3 | |
| 9.18.4 | 3 / 3 | |
| 9.18.3 | 3 / 3 | |
| 9.18.2 | 3 / 3 | |
| 9.18.1 | 3 / 3 | |
| 9.18.0 | 3 / 3 | |
| 9.17.0 | 3 / 3 | |
| 9.16.1 | 3 / 3 | |
| 9.16.0 | 3 / 3 | |
| 9.15.6 | 3 / 3 | |
| 9.15.5 | 3 / 3 | |
| 9.15.4 | 3 / 3 | |
| 9.15.3 | 3 / 3 | |
| 9.15.2 | 2 / 3 | |
| 9.15.1 | 2 / 3 | |
| 9.15.0 | 2 / 3 | |
| 9.14.2 | 2 / 3 | |
| 9.14.1 | 2 / 3 | |
| 9.14.0 | 2 / 3 | |
| 9.13.5 | 2 / 3 | |
| 9.13.4 | 2 / 3 | |
| 9.13.3 | 2 / 3 | |
| 9.13.2 | 2 / 3 | |
| 9.13.1 | 2 / 3 | |
| 9.13.0 | 2 / 3 | |
| 9.12.0 | 2 / 3 | |
| 9.11.2 | 2 / 3 | |
| 9.11.1 | 2 / 3 | |
| 9.11.0 | 2 / 3 | |
| 9.10.1 | 2 / 3 | |
| 9.10.0 | 2 / 3 | |
| 9.9.4 | 2 / 3 | |
| 9.9.3 | 2 / 3 | |
| 9.9.2 | 2 / 3 | |
| 9.9.1 | 2 / 3 | |
| 9.9.0 | 2 / 3 | |
| 9.8.1 | 2 / 3 | |
| 9.8.0 | 2 / 3 | |
| 9.7.4 | 2 / 3 | |
| 9.7.3 | 2 / 3 | |
| 9.7.2 | 2 / 3 | |
| 9.7.1 | 2 / 3 | |
| 9.7.0 | 2 / 3 | |
| 9.6.2 | 2 / 3 | |
| 9.6.1 | 2 / 3 | |
| 9.6.0 | 2 / 3 | |
| 9.5.3 | 2 / 3 | |
| 9.5.2 | 2 / 3 | |
| 9.5.1 | 2 / 3 | |
| 9.5.0 | 2 / 3 | |
| 9.4.0 | 2 / 2 | |
| 9.3.1 | 2 / 2 | |
| 9.3.0 | 2 / 2 | |
| 9.2.2 | 2 / 2 | |
| 9.2.1 | 2 / 2 | |
| 9.2.0 | 2 / 2 | |
| 9.1.2 | 2 / 2 | |
| 9.1.1 | 2 / 2 | |
| 9.1.0 | 2 / 2 | |
| 9.0.2 | 2 / 2 | |
| 9.0.0 | 2 / 2 |
v9.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.