@fluentui/react-dialog
Dialog component for Fluent UI React
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:@fluentui/react-motions-preview | AI (dependencies): First-party @fluentui monorepo package, same publisher/org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Internal Fluent UI dependency swap, not a third-party supply-chain addition. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-portal | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft's Fluent UI monorepo publishes without Sigstore provenance; this is consistent across all versions and not a security concern for this well-established package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-motion-components-preview | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | ai | |
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is Microsoft's CSS-in-JS engine built specifically for Fluent UI; a legitimate, expected dependency for this package. | ai |
Versions (showing 82 of 182)
| Version | Deps | Published |
|---|---|---|
| 9.9.2 | 13 / 6 | |
| 9.9.1 | 13 / 6 | |
| 9.9.0 | 13 / 6 | |
| 9.8.7 | 13 / 6 | |
| 9.8.6 | 13 / 6 | |
| 9.8.5 | 13 / 6 | |
| 9.8.4 | 13 / 6 | |
| 9.8.3 | 13 / 6 | |
| 9.8.2 | 13 / 6 | |
| 9.8.1 | 13 / 6 | |
| 9.8.0 | 13 / 6 | |
| 9.7.10 | 12 / 6 | |
| 9.7.9 | 12 / 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.1 | 12 / 6 | |
| 9.7.0 | 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 / 6 | |
| 9.6.0 | 12 / 6 | |
| 9.5.26 | 12 / 6 | |
| 9.5.25 | 12 / 6 | |
| 9.5.24 | 12 / 6 | |
| 9.5.23 | 12 / 6 | |
| 9.5.22 | 12 / 6 | |
| 9.5.21 | 12 / 6 | |
| 9.5.20 | 12 / 6 | |
| 9.5.19 | 12 / 6 | |
| 9.5.18 | 12 / 6 | |
| 9.5.17 | 12 / 6 | |
| 9.5.16 | 12 / 6 | |
| 9.5.15 | 12 / 6 | |
| 9.5.14 | 12 / 6 | |
| 9.5.13 | 12 / 6 | |
| 9.5.12 | 12 / 6 | |
| 9.5.11 | 12 / 6 | |
| 9.5.10 | 12 / 6 | |
| 9.5.9 | 12 / 6 | |
| 9.5.8 | 12 / 6 | |
| 9.5.7 | 12 / 6 | |
| 9.5.6 | 12 / 6 | |
| 9.5.5 | 12 / 6 | |
| 9.5.4 | 12 / 6 | |
| 9.5.3 | 12 / 6 | |
| 9.5.2 | 12 / 6 | |
| 9.5.1 | 11 / 6 | |
| 9.5.0 | 11 / 6 | |
| 9.4.3 | 11 / 6 | |
| 9.4.2 | 11 / 6 | |
| 9.4.1 | 11 / 6 | |
| 9.4.0 | 11 / 6 | |
| 9.3.2 | 11 / 6 | |
| 9.3.1 | 11 / 6 | |
| 9.3.0 | 11 / 6 | |
| 9.2.0 | 11 / 6 | |
| 9.1.16 | 11 / 6 | |
| 9.1.15 | 11 / 6 | |
| 9.1.14 | 11 / 6 | |
| 9.1.13 | 11 / 6 | |
| 9.1.12 | 11 / 6 | |
| 9.1.11 | 11 / 6 | |
| 9.1.10 | 11 / 6 | |
| 9.1.9 | 11 / 6 | |
| 9.1.8 | 11 / 6 | |
| 9.1.7 | 11 / 4 | |
| 9.1.6 | 11 / 4 | |
| 9.1.5 | 11 / 4 | |
| 9.1.4 | 11 / 4 | |
| 9.1.3 | 11 / 4 | |
| 9.1.2 | 11 / 4 | |
| 9.1.1 | 11 / 4 | |
| 9.1.0 | 11 / 4 | |
| 9.0.3 | 11 / 4 | |
| 9.0.2 | 11 / 4 | |
| 9.0.0 | 11 / 4 |
v9.9.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.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.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.8.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.8.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.8.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.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.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.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.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.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.5.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.5.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.5.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.5.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.5.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.5.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.5.19
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.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.5.17
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.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.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.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.4.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.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.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.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.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.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.1.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.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.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.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.