@fluentui/react-tooltip
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 v9, maintained by Microsoft. Expected dependency for all @fluentui/react-* components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-portal | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency for tooltip rendering. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency for accessibility/focus management. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-positioning | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency for tooltip positioning logic. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui sibling package from Microsoft's Fluent UI monorepo. Expected dependency. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and no keywords are typical for sub-packages in large component library monorepos like @fluentui. Not indicative of spam or malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): Fluent UI packages are published by Microsoft's uifabricteam; lack of Sigstore provenance is common and not a risk signal for this well-established publisher. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 9.10.2 | 10 / 0 | |
| 9.10.1 | 10 / 0 | |
| 9.10.0 | 10 / 0 | |
| 9.9.3 | 10 / 0 | |
| 9.9.2 | 10 / 0 | |
| 9.9.1 | 10 / 0 | |
| 9.9.0 | 10 / 0 | |
| 9.8.12 | 10 / 4 | |
| 9.8.11 | 10 / 4 | |
| 9.8.10 | 10 / 4 | |
| 9.8.9 | 10 / 4 | |
| 9.8.8 | 10 / 4 | |
| 9.8.7 | 10 / 4 | |
| 9.8.6 | 10 / 4 | |
| 9.8.5 | 10 / 4 | |
| 9.8.4 | 10 / 4 | |
| 9.8.3 | 10 / 4 | |
| 9.8.2 | 10 / 4 | |
| 9.8.1 | 10 / 4 | |
| 9.8.0 | 10 / 4 | |
| 9.7.7 | 10 / 4 | |
| 9.7.6 | 10 / 4 | |
| 9.7.5 | 10 / 4 | |
| 9.7.4 | 10 / 4 | |
| 9.7.3 | 10 / 4 | |
| 9.7.2 | 10 / 4 | |
| 9.7.1 | 10 / 4 | |
| 9.7.0 | 10 / 4 | |
| 9.6.9 | 10 / 4 | |
| 9.6.8 | 10 / 4 | |
| 9.6.7 | 10 / 4 |
v9.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.