@fluentui/react-menu
Fluent UI menu component
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Fluent UI component packages document via external docs/Storybook; short README and no keywords are expected for this ecosystem, not spam indicators. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft Fluent UI package; lack of Sigstore provenance is common and not a risk signal for this well-known publisher. | ai | |
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): Griffel is Microsoft's CSS-in-JS library, part of the Fluent UI ecosystem. Unvetted status reflects pipeline gap, not real risk. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-portal | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-positioning | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion-components-preview | AI (dependencies): First-party Fluent UI sibling package from Microsoft; unvetted status is a pipeline gap. | ai |
Versions (showing 85 of 185)
| Version | Deps | Published |
|---|---|---|
| 9.12.28 | 13 / 6 | |
| 9.12.27 | 13 / 6 | |
| 9.12.26 | 13 / 6 | |
| 9.12.25 | 13 / 6 | |
| 9.12.24 | 13 / 6 | |
| 9.12.23 | 13 / 6 | |
| 9.12.22 | 13 / 6 | |
| 9.12.21 | 13 / 6 | |
| 9.12.20 | 13 / 6 | |
| 9.12.18 | 13 / 6 | |
| 9.12.16 | 13 / 6 | |
| 9.12.15 | 13 / 6 | |
| 9.12.14 | 13 / 6 | |
| 9.12.13 | 13 / 6 | |
| 9.12.12 | 13 / 6 | |
| 9.12.11 | 13 / 6 | |
| 9.12.10 | 13 / 6 | |
| 9.12.9 | 13 / 6 | |
| 9.12.8 | 13 / 6 | |
| 9.12.7 | 13 / 6 | |
| 9.12.6 | 13 / 6 | |
| 9.12.5 | 13 / 6 | |
| 9.12.4 | 13 / 6 | |
| 9.12.3 | 13 / 6 | |
| 9.12.2 | 13 / 6 | |
| 9.12.1 | 13 / 6 | |
| 9.12.0 | 13 / 6 | |
| 9.11.1 | 13 / 6 | |
| 9.11.0 | 13 / 6 | |
| 9.10.0 | 13 / 6 | |
| 9.9.1 | 13 / 6 | |
| 9.9.0 | 13 / 6 | |
| 9.8.3 | 13 / 6 | |
| 9.8.2 | 13 / 6 | |
| 9.8.1 | 13 / 6 | |
| 9.8.0 | 13 / 6 | |
| 9.7.16 | 13 / 6 | |
| 9.7.15 | 13 / 6 | |
| 9.7.14 | 13 / 6 | |
| 9.7.13 | 13 / 6 | |
| 9.7.12 | 13 / 6 | |
| 9.7.11 | 13 / 6 | |
| 9.7.10 | 13 / 6 | |
| 9.7.9 | 13 / 6 | |
| 9.7.8 | 12 / 6 | |
| 9.7.7 | 12 / 6 | |
| 9.7.6 | 12 / 6 | |
| 9.7.5 | 12 / 6 | |
| 9.7.4 | 12 / 6 | |
| 9.7.3 | 12 / 6 | |
| 9.7.2 | 12 / 6 | |
| 9.7.1 | 12 / 6 | |
| 9.7.0 | 12 / 6 | |
| 9.6.12 | 12 / 6 | |
| 9.6.11 | 12 / 6 | |
| 9.6.10 | 12 / 6 | |
| 9.6.9 | 12 / 6 | |
| 9.6.8 | 12 / 6 | |
| 9.6.7 | 12 / 6 | |
| 9.6.6 | 12 / 6 | |
| 9.6.5 | 12 / 6 | |
| 9.6.4 | 12 / 6 | |
| 9.6.3 | 12 / 6 | |
| 9.6.2 | 12 / 6 | |
| 9.6.1 | 12 / 4 | |
| 9.6.0 | 12 / 4 | |
| 9.5.4 | 12 / 4 | |
| 9.5.3 | 12 / 4 | |
| 9.5.2 | 12 / 4 | |
| 9.5.1 | 12 / 4 | |
| 9.5.0 | 12 / 4 | |
| 9.4.1 | 12 / 4 | |
| 9.4.0 | 12 / 4 | |
| 9.3.1 | 12 / 4 | |
| 9.3.0 | 12 / 4 | |
| 9.2.3 | 12 / 4 | |
| 9.2.2 | 12 / 4 | |
| 9.2.1 | 12 / 4 | |
| 9.2.0 | 12 / 4 | |
| 9.1.0 | 12 / 4 | |
| 9.0.4 | 11 / 4 | |
| 9.0.3 | 11 / 4 | |
| 9.0.2 | 11 / 4 | |
| 9.0.1 | 11 / 4 | |
| 9.0.0 | 11 / 4 |
v9.12.28
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.27
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.26
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.25
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.24
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.23
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.22
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.21
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.20
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.18
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.16
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.15
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.14
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.13
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.12
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.11
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.12.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.12.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.
v9.12.6
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.5
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.4
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.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.
v9.12.2
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.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.12.0
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.11.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.11.0
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.0
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.9.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.9.0
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.8.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.
v9.8.2
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.8.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.8.0
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.7.16
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.7.15
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.7.14
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.7.13
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.7.12
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.7.11
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.7.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.7.9
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.7.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.7.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.
v9.7.6
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.7.5
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.7.4
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.7.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.
v9.7.2
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.7.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.7.0
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.6.12
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.6.11
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.6.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.6.9
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.6.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.6.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.
v9.6.6
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.6.5
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.6.4
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.6.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.
v9.6.2
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.6.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.6.0
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.5.4
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.5.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.
v9.5.2
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.5.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.5.0
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.4.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.4.0
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.3.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.3.0
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.2.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.
v9.2.2
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.2.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.2.0
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.1.0
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.0.4
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.0.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.
v9.0.2
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.0.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.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.