@fluentui/react-combobox
Fluent UI React Combobox 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 — 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@griffel/react | AI (dependencies): @griffel/react is the official CSS-in-JS library for Fluent UI v9, maintained by Microsoft. Standard dependency for this package. | ai | |
| dependencies | unvetted-dep:@fluentui/react-aria | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-field | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): Official Fluent UI icons package from Microsoft. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-portal | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/keyboard-keys | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-tabster | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-positioning | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-context-selector | AI (dependencies): Official Fluent UI v9 sibling package from Microsoft's monorepo. Expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft Fluent UI monorepo package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and no keywords are typical of monorepo sub-packages; not indicative of spam or malicious intent. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 9.17.2 | 14 / 0 | |
| 9.17.1 | 14 / 0 | |
| 9.17.0 | 14 / 0 | |
| 9.16.18 | 14 / 0 | |
| 9.16.17 | 14 / 0 | |
| 9.16.16 | 14 / 0 | |
| 9.16.15 | 14 / 0 | |
| 9.16.14 | 14 / 0 | |
| 9.16.13 | 14 / 5 | |
| 9.16.12 | 14 / 5 | |
| 9.16.11 | 14 / 5 | |
| 9.16.10 | 14 / 5 | |
| 9.16.9 | 14 / 5 | |
| 9.16.8 | 14 / 5 | |
| 9.16.7 | 14 / 5 | |
| 9.16.6 | 14 / 5 | |
| 9.16.5 | 14 / 5 | |
| 9.16.4 | 14 / 5 | |
| 9.16.3 | 14 / 5 | |
| 9.16.2 | 14 / 5 | |
| 9.16.1 | 14 / 5 | |
| 9.16.0 | 14 / 5 | |
| 9.15.7 | 14 / 5 | |
| 9.15.6 | 14 / 5 | |
| 9.15.5 | 14 / 5 | |
| 9.15.4 | 14 / 5 | |
| 9.15.3 | 14 / 5 | |
| 9.15.2 | 14 / 5 | |
| 9.15.1 | 14 / 5 | |
| 9.15.0 | 14 / 5 | |
| 9.14.9 | 14 / 5 | |
| 9.14.8 | 14 / 5 | |
| 9.14.7 | 14 / 5 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.17.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.16.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.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.16.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.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.16.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.16.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.16.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.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.7
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. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.14.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.14.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.