@fluentui-react-native/experimental-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted bot publisher across monorepo; benign tooling change, not credential compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party sibling package in same monorepo. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/button | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo, published by the same trusted bot publisher. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/framework | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo, published by the same trusted bot publisher. | ai | |
| dependencies | unvetted-dep:@fluentui-react-native/contextual-menu | AI (dependencies): Sibling package within the same Microsoft FluentUI React Native monorepo, published by the same trusted bot publisher. | ai |
Versions (showing 100 of 322)
| Version | Deps | Published |
|---|---|---|
| 0.11.5 | 5 / 16 | |
| 0.11.4 | 4 / 17 | |
| 0.11.3 | 4 / 21 | |
| 0.11.1 | 4 / 21 | |
| 0.11.0 | 4 / 21 | |
| 0.10.37 | 4 / 16 | |
| 0.10.36 | 4 / 16 | |
| 0.10.35 | 4 / 16 | |
| 0.10.34 | 4 / 16 | |
| 0.10.33 | 4 / 16 | |
| 0.10.32 | 4 / 16 | |
| 0.10.31 | 4 / 16 | |
| 0.10.30 | 4 / 16 | |
| 0.10.29 | 4 / 16 | |
| 0.10.28 | 4 / 12 | |
| 0.10.27 | 4 / 12 | |
| 0.10.26 | 4 / 12 | |
| 0.10.25 | 4 / 12 | |
| 0.10.24 | 4 / 12 | |
| 0.10.23 | 4 / 12 | |
| 0.10.22 | 4 / 12 | |
| 0.10.21 | 4 / 12 | |
| 0.10.20 | 4 / 10 | |
| 0.10.19 | 4 / 8 | |
| 0.10.18 | 4 / 8 | |
| 0.10.17 | 4 / 8 | |
| 0.10.16 | 4 / 8 | |
| 0.10.15 | 4 / 8 | |
| 0.10.14 | 4 / 8 | |
| 0.10.13 | 4 / 8 | |
| 0.10.12 | 4 / 8 | |
| 0.10.11 | 4 / 8 | |
| 0.10.10 | 4 / 8 | |
| 0.10.9 | 4 / 8 | |
| 0.10.8 | 4 / 8 | |
| 0.10.7 | 4 / 8 | |
| 0.10.6 | 4 / 8 | |
| 0.10.5 | 4 / 8 | |
| 0.10.4 | 4 / 8 | |
| 0.10.3 | 4 / 8 | |
| 0.10.2 | 4 / 8 | |
| 0.10.1 | 4 / 8 | |
| 0.10.0 | 4 / 8 | |
| 0.9.21 | 4 / 7 | |
| 0.9.20 | 4 / 7 | |
| 0.9.19 | 4 / 7 | |
| 0.9.18 | 4 / 7 | |
| 0.9.17 | 4 / 7 | |
| 0.9.16 | 4 / 7 | |
| 0.9.15 | 4 / 7 | |
| 0.9.14 | 4 / 7 | |
| 0.9.13 | 4 / 7 | |
| 0.9.12 | 4 / 7 | |
| 0.9.11 | 4 / 7 | |
| 0.9.10 | 4 / 7 | |
| 0.9.9 | 4 / 7 | |
| 0.9.8 | 4 / 7 | |
| 0.9.7 | 4 / 7 | |
| 0.9.6 | 4 / 7 | |
| 0.9.5 | 4 / 7 | |
| 0.9.4 | 4 / 7 | |
| 0.9.3 | 4 / 7 | |
| 0.9.2 | 4 / 7 | |
| 0.9.1 | 4 / 7 | |
| 0.9.0 | 4 / 7 | |
| 0.8.1 | 4 / 7 | |
| 0.8.0 | 4 / 7 | |
| 0.7.31 | 4 / 6 | |
| 0.7.30 | 4 / 6 | |
| 0.7.29 | 4 / 6 | |
| 0.7.28 | 4 / 6 | |
| 0.7.27 | 4 / 6 | |
| 0.7.26 | 4 / 6 | |
| 0.7.25 | 4 / 6 | |
| 0.7.24 | 4 / 6 | |
| 0.7.23 | 4 / 6 | |
| 0.7.22 | 4 / 6 | |
| 0.7.21 | 4 / 6 | |
| 0.7.20 | 4 / 6 | |
| 0.7.19 | 4 / 6 | |
| 0.7.18 | 4 / 6 | |
| 0.7.17 | 4 / 6 | |
| 0.7.16 | 4 / 6 | |
| 0.7.15 | 4 / 6 | |
| 0.7.14 | 4 / 6 | |
| 0.7.13 | 4 / 6 | |
| 0.7.12 | 4 / 6 | |
| 0.7.11 | 4 / 6 | |
| 0.7.10 | 4 / 6 | |
| 0.7.9 | 4 / 6 | |
| 0.7.8 | 4 / 6 | |
| 0.7.7 | 4 / 6 | |
| 0.7.6 | 4 / 6 | |
| 0.7.5 | 4 / 6 | |
| 0.7.4 | 4 / 6 | |
| 0.7.3 | 4 / 6 | |
| 0.7.2 | 4 / 6 | |
| 0.7.1 | 4 / 6 | |
| 0.7.0 | 4 / 6 | |
| 0.6.52 | 4 / 7 |
v0.11.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: uifrnbot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.