@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 — the axios compromise (March 2026) relied on exactly this gap.
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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 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 |
v9.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.