@fluentui/react-tree
Tree component for Fluent UI React
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. Legitimate dependency for all @fluentui/* packages. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-radio | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-avatar | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-button | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-checkbox | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion-components-preview | AI (dependencies): First-party @fluentui/* package from Microsoft's Fluent UI monorepo. Legitimate dependency. | ai | |
| phantom-deps | phantom-dep:@fluentui/react-aria | AI (phantom-deps): Same org scope; common in monorepo packages where transitive usage patterns differ from direct imports. Not a risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large monorepo component packages often lack standalone README code blocks and keywords; not indicative of spam for established Microsoft Fluent UI packages. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 9.16.1 | 17 / 0 | |
| 9.16.0 | 17 / 0 | |
| 9.15.16 | 17 / 0 | |
| 9.15.15 | 17 / 0 | |
| 9.15.14 | 17 / 0 | |
| 9.15.13 | 17 / 0 | |
| 9.15.12 | 17 / 0 | |
| 9.15.11 | 17 / 0 | |
| 9.15.10 | 17 / 0 | |
| 9.15.9 | 17 / 0 | |
| 9.15.8 | 17 / 6 | |
| 9.15.7 | 17 / 6 | |
| 9.15.6 | 17 / 6 | |
| 9.15.5 | 17 / 6 | |
| 9.15.4 | 17 / 6 | |
| 9.15.3 | 17 / 6 | |
| 9.15.2 | 17 / 6 | |
| 9.15.1 | 17 / 6 | |
| 9.15.0 | 17 / 6 | |
| 9.14.1 | 17 / 6 | |
| 9.14.0 | 17 / 6 | |
| 9.13.1 | 17 / 6 | |
| 9.13.0 | 17 / 6 | |
| 9.12.4 | 17 / 6 | |
| 9.12.3 | 17 / 6 | |
| 9.12.2 | 17 / 6 | |
| 9.12.1 | 17 / 6 | |
| 9.12.0 | 17 / 6 | |
| 9.11.8 | 17 / 6 | |
| 9.11.7 | 17 / 6 | |
| 9.11.6 | 17 / 6 | |
| 9.11.5 | 17 / 6 | |
| 9.11.4 | 17 / 6 | |
| 9.11.3 | 17 / 6 | |
| 9.11.2 | 17 / 6 | |
| 9.11.1 | 17 / 6 | |
| 9.11.0 | 17 / 6 | |
| 9.10.12 | 17 / 6 | |
| 9.10.11 | 17 / 6 | |
| 9.10.10 | 17 / 6 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.15.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.15.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.15.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.1
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.3
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.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.