@fluentui-react-native/contextual-menu
A cross-platform ContextualMenu 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-native-community/hooks | AI (dependencies): Established, widely-used community RN hooks package; benign addition. | ai | |
| provenance | missing-githead | AI (provenance): Monorepo build-tooling change, consistent across sibling packages, not a hijack indicator. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a first-party sibling package in the same monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Large Microsoft monorepo package published via CI bot; lack of Sigstore provenance is consistent across all versions and not a meaningful risk signal for this package. | ai |
Versions (showing 51 of 346)
| Version | Deps | Published |
|---|---|---|
| 0.25.5 | 11 / 20 | |
| 0.25.4 | 10 / 21 | |
| 0.25.3 | 10 / 25 | |
| 0.25.1 | 10 / 25 | |
| 0.25.0 | 10 / 25 | |
| 0.24.31 | 10 / 19 | |
| 0.24.30 | 10 / 19 | |
| 0.24.29 | 10 / 19 | |
| 0.24.28 | 10 / 19 | |
| 0.24.27 | 10 / 19 | |
| 0.24.26 | 10 / 19 | |
| 0.24.25 | 10 / 14 | |
| 0.24.24 | 10 / 14 | |
| 0.24.23 | 10 / 14 | |
| 0.24.22 | 10 / 14 | |
| 0.24.21 | 10 / 14 | |
| 0.24.20 | 10 / 14 | |
| 0.24.19 | 10 / 14 | |
| 0.24.18 | 10 / 14 | |
| 0.24.17 | 10 / 12 | |
| 0.24.16 | 10 / 10 | |
| 0.24.15 | 10 / 10 | |
| 0.24.14 | 10 / 10 | |
| 0.24.13 | 10 / 10 | |
| 0.24.12 | 10 / 10 | |
| 0.24.11 | 10 / 10 | |
| 0.24.10 | 10 / 10 | |
| 0.24.9 | 10 / 10 | |
| 0.24.8 | 10 / 10 | |
| 0.24.7 | 10 / 10 | |
| 0.24.6 | 10 / 10 | |
| 0.24.5 | 10 / 10 | |
| 0.24.4 | 10 / 10 | |
| 0.24.3 | 10 / 10 | |
| 0.24.2 | 10 / 10 | |
| 0.24.1 | 10 / 10 | |
| 0.24.0 | 10 / 10 | |
| 0.23.19 | 10 / 9 | |
| 0.23.18 | 10 / 9 | |
| 0.23.17 | 10 / 9 | |
| 0.23.16 | 10 / 9 | |
| 0.23.15 | 10 / 9 | |
| 0.23.14 | 10 / 9 | |
| 0.23.13 | 10 / 9 | |
| 0.23.12 | 10 / 9 | |
| 0.23.11 | 10 / 9 | |
| 0.23.10 | 10 / 9 | |
| 0.23.9 | 10 / 9 | |
| 0.23.8 | 10 / 9 | |
| 0.23.7 | 10 / 9 | |
| 0.23.6 | 10 / 9 |
v0.25.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
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.24.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.