@fluentui/react-toolbar
React components for building web experiences
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS engine for Fluent UI, maintained by Microsoft. Expected dependency for all @fluentui/* component packages. | ai | |
| dependencies | unvetted-dep:@fluentui/react-radio | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-button | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-divider | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party @fluentui/* monorepo dependency from Microsoft. Expected for this component package. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-radio | AI (phantom-deps): Same-org monorepo package; declared but not directly imported is a common pattern in Fluent UI's monorepo component structure. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and no keywords are typical of monorepo sub-packages that rely on the root repo documentation. Not indicative of spam for this established Microsoft package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 9.8.1 | 11 / 0 | |
| 9.8.0 | 11 / 0 | |
| 9.7.7 | 11 / 0 | |
| 9.7.6 | 11 / 0 | |
| 9.7.5 | 11 / 0 | |
| 9.7.4 | 11 / 0 | |
| 9.7.3 | 11 / 0 | |
| 9.7.2 | 11 / 0 | |
| 9.7.1 | 11 / 0 | |
| 9.7.0 | 11 / 0 | |
| 9.6.14 | 11 / 6 | |
| 9.6.13 | 11 / 6 | |
| 9.6.12 | 11 / 6 | |
| 9.6.11 | 11 / 6 | |
| 9.6.10 | 11 / 6 | |
| 9.6.9 | 11 / 6 | |
| 9.6.8 | 11 / 6 | |
| 9.6.7 | 11 / 6 | |
| 9.6.6 | 11 / 6 | |
| 9.6.5 | 11 / 6 | |
| 9.6.4 | 11 / 6 | |
| 9.6.3 | 11 / 6 | |
| 9.6.2 | 11 / 6 | |
| 9.6.1 | 11 / 6 | |
| 9.6.0 | 11 / 6 | |
| 9.5.8 | 11 / 6 | |
| 9.5.7 | 11 / 6 | |
| 9.5.6 | 11 / 6 | |
| 9.5.5 | 11 / 6 | |
| 9.5.4 | 11 / 6 | |
| 9.5.3 | 11 / 6 | |
| 9.5.2 | 11 / 6 | |
| 9.5.1 | 11 / 6 | |
| 9.5.0 | 11 / 6 | |
| 9.4.8 | 11 / 6 | |
| 9.4.7 | 11 / 6 | |
| 9.4.6 | 11 / 6 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.3
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.