@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 — 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 |
|---|---|---|---|---|
| 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:@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 | |
| 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 | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): First-party @fluentui sibling package from the microsoft/fluentui monorepo; expected dependency. | 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 |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 9.18.1 | 14 / 0 | |
| 9.18.0 | 14 / 0 | |
| 9.17.3 | 14 / 0 | |
| 9.17.2 | 14 / 0 | |
| 9.17.1 | 14 / 0 | |
| 9.17.0 | 14 / 0 | |
| 9.16.6 | 14 / 0 | |
| 9.16.5 | 14 / 10 | |
| 9.16.4 | 14 / 10 | |
| 9.16.3 | 14 / 10 | |
| 9.16.2 | 14 / 10 | |
| 9.16.1 | 14 / 10 | |
| 9.16.0 | 14 / 10 | |
| 9.15.5 | 14 / 10 | |
| 9.15.4 | 14 / 10 | |
| 9.15.3 | 14 / 10 | |
| 9.15.2 | 14 / 10 | |
| 9.15.1 | 14 / 10 | |
| 9.15.0 | 14 / 10 | |
| 9.14.4 | 14 / 10 | |
| 9.14.3 | 14 / 10 | |
| 9.14.2 | 14 / 10 | |
| 9.14.1 | 14 / 10 | |
| 9.14.0 | 14 / 10 | |
| 9.13.8 | 14 / 10 | |
| 9.13.7 | 14 / 10 | |
| 9.13.6 | 14 / 10 | |
| 9.13.5 | 14 / 10 | |
| 9.13.4 | 14 / 10 | |
| 9.13.3 | 14 / 10 | |
| 9.13.2 | 14 / 10 | |
| 9.13.1 | 14 / 10 | |
| 9.13.0 | 14 / 10 | |
| 9.12.11 | 14 / 10 | |
| 9.12.10 | 14 / 10 | |
| 9.12.9 | 14 / 10 |
v9.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.17.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.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.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.16.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.16.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.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.