@fluentui/react-search
Search input for Fluent UI v9
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. It is a stable, expected dependency for all @fluentui/react-* components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-icons | AI (dependencies): First-party Microsoft Fluent UI package from the same monorepo (github.com/microsoft/fluentui). Expected dependency. | ai | |
| dependencies | unvetted-dep:@fluentui/react-input | AI (dependencies): First-party Microsoft Fluent UI package from the same monorepo. Expected dependency for a search input component. | ai | |
| dependencies | unvetted-dep:@fluentui/react-theme | AI (dependencies): First-party Microsoft Fluent UI package from the same monorepo. Standard theming dependency for all Fluent UI v9 components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-utilities | AI (dependencies): First-party Microsoft Fluent UI package from the same monorepo. Standard utilities dependency for all Fluent UI v9 components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-jsx-runtime | AI (dependencies): First-party Microsoft Fluent UI package from the same monorepo. Standard JSX runtime dependency for Fluent UI v9 components. | ai | |
| dependencies | unvetted-dep:@fluentui/react-shared-contexts | AI (dependencies): First-party Microsoft Fluent UI package from the same monorepo. Standard shared contexts dependency for Fluent UI v9 components. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft's Fluent UI monorepo publishes without Sigstore provenance; this is consistent across all @fluentui/* packages and is not a security concern given the established publisher. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 9.4.3 | 8 / 0 | |
| 9.4.2 | 8 / 0 | |
| 9.4.1 | 8 / 0 | |
| 9.4.0 | 8 / 0 | |
| 9.3.16 | 8 / 0 | |
| 9.3.15 | 8 / 0 | |
| 9.3.14 | 8 / 0 | |
| 9.3.13 | 8 / 0 | |
| 9.3.12 | 8 / 4 | |
| 9.3.11 | 8 / 4 | |
| 9.3.10 | 8 / 4 | |
| 9.3.9 | 8 / 4 | |
| 9.3.8 | 8 / 4 | |
| 9.3.7 | 8 / 4 | |
| 9.3.6 | 8 / 4 | |
| 9.3.5 | 8 / 4 | |
| 9.3.4 | 8 / 4 | |
| 9.3.3 | 8 / 4 | |
| 9.3.2 | 8 / 4 | |
| 9.3.1 | 8 / 4 | |
| 9.3.0 | 8 / 4 | |
| 9.2.7 | 8 / 4 | |
| 9.2.6 | 8 / 4 | |
| 9.2.5 | 8 / 4 | |
| 9.2.4 | 8 / 4 | |
| 9.2.3 | 8 / 4 | |
| 9.2.2 | 8 / 4 | |
| 9.2.1 | 8 / 4 | |
| 9.2.0 | 8 / 4 | |
| 9.1.9 | 8 / 4 | |
| 9.1.8 | 8 / 4 | |
| 9.1.7 | 8 / 4 |
v9.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
1 findingPackage 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.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.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.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.