@fluentui-react-native/menu-button
A cross-platform MenuButton 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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package from Microsoft's FluentUI RN project; sparse README and no keywords are typical for such packages and not indicative of spam. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft OSS package published via bot; lack of Sigstore provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.14.3 | 7 / 21 | |
| 0.14.1 | 7 / 21 | |
| 0.14.0 | 7 / 21 | |
| 0.13.37 | 7 / 16 | |
| 0.13.36 | 7 / 16 | |
| 0.13.35 | 7 / 16 | |
| 0.13.34 | 7 / 16 | |
| 0.13.33 | 7 / 16 | |
| 0.13.32 | 7 / 16 | |
| 0.13.31 | 7 / 16 | |
| 0.13.30 | 7 / 16 | |
| 0.13.29 | 7 / 16 | |
| 0.13.28 | 7 / 12 | |
| 0.13.27 | 7 / 12 | |
| 0.13.26 | 7 / 12 | |
| 0.13.25 | 7 / 12 | |
| 0.13.24 | 7 / 12 | |
| 0.13.23 | 7 / 12 | |
| 0.13.22 | 7 / 12 | |
| 0.13.21 | 7 / 12 | |
| 0.13.20 | 7 / 10 |
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.