@fluentui-react-native/popover
A cross-platform Popover component using the Fluent Design System
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:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same Microsoft fluentui-react-native monorepo; not a third-party risk. Stable false positive for this package. | ai | |
| dependencies | unvetted-peer-dep:react-native-macos | AI (dependencies): Optional platform-specific peer dependency for macOS support; standard pattern for cross-platform React Native libraries. | ai | |
| dependencies | unvetted-peer-dep:react-native-windows | AI (dependencies): Optional platform-specific peer dependency for Windows support; standard pattern for cross-platform React Native libraries. | ai | |
| dependencies | unvetted-peer-dep:@office-iss/react-native-win32 | AI (dependencies): Optional peer dependency for Office Win32 platform support; expected for Microsoft FluentUI components targeting Windows. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 2 / 15 | |
| 0.5.1 | 2 / 15 | |
| 0.5.0 | 2 / 15 | |
| 0.4.17 | 2 / 11 | |
| 0.4.16 | 2 / 11 | |
| 0.4.15 | 2 / 11 | |
| 0.4.14 | 2 / 11 | |
| 0.4.13 | 2 / 11 | |
| 0.4.12 | 2 / 11 | |
| 0.4.11 | 3 / 10 | |
| 0.4.10 | 3 / 10 | |
| 0.4.9 | 3 / 10 | |
| 0.4.8 | 3 / 10 | |
| 0.4.7 | 3 / 10 | |
| 0.4.6 | 3 / 10 | |
| 0.4.5 | 3 / 10 | |
| 0.4.4 | 3 / 10 | |
| 0.4.3 | 3 / 8 |
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.