@fluentui/react-popover
Popover component for Fluent UI
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 Microsoft's official CSS-in-JS library for Fluent UI, a legitimate and expected dependency for all @fluentui/* components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-portal | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-positioning | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion-components-preview | AI (dependencies): First-party @fluentui/* sibling package from the Microsoft Fluent UI monorepo; expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft's Fluent UI packages do not currently publish Sigstore provenance; this is consistent across all versions and not a security concern for this well-established publisher. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.14.3 | 14 / 0 | |
| 9.14.2 | 14 / 0 | |
| 9.14.1 | 14 / 0 | |
| 9.14.0 | 14 / 0 | |
| 9.13.2 | 12 / 0 | |
| 9.13.1 | 12 / 0 | |
| 9.13.0 | 12 / 0 | |
| 9.12.13 | 12 / 7 | |
| 9.12.12 | 12 / 7 | |
| 9.12.11 | 12 / 7 | |
| 9.12.10 | 12 / 7 | |
| 9.12.9 | 12 / 7 | |
| 9.12.8 | 12 / 7 | |
| 9.12.7 | 12 / 7 | |
| 9.12.6 | 12 / 7 | |
| 9.12.5 | 12 / 7 | |
| 9.12.4 | 12 / 7 | |
| 9.12.3 | 12 / 7 | |
| 9.12.2 | 12 / 7 | |
| 9.12.1 | 12 / 7 | |
| 9.12.0 | 12 / 7 | |
| 9.11.7 | 12 / 7 | |
| 9.11.6 | 12 / 7 | |
| 9.11.5 | 12 / 7 | |
| 9.11.4 | 12 / 7 | |
| 9.11.3 | 12 / 7 | |
| 9.11.2 | 12 / 7 | |
| 9.11.1 | 12 / 7 | |
| 9.11.0 | 12 / 7 | |
| 9.10.9 | 12 / 7 | |
| 9.10.8 | 12 / 7 | |
| 9.10.7 | 12 / 7 |
v9.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.14.1
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.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.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.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.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.10.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.