@fluentui/react-select MIT 31 versions

@fluentui/react-select

npm Repository Homepage

Fluent UI React Select component

31

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

chrisdholtmiroslavstastnylevithomasonuifabricteamuifrnbotlayershifterjustslonemicrosoft1essopranopillow

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 engine for Fluent UI, maintained by Microsoft. Expected dependency for all @fluentui/* components.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-field	AI (dependencies): First-party @fluentui/* monorepo sibling package from Microsoft. Expected dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-icons	AI (dependencies): First-party @fluentui/* monorepo sibling package from Microsoft. Expected dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-theme	AI (dependencies): First-party @fluentui/* monorepo sibling package from Microsoft. Expected dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-utilities	AI (dependencies): First-party @fluentui/* monorepo sibling package from Microsoft. Expected dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-jsx-runtime	AI (dependencies): First-party @fluentui/* monorepo sibling package from Microsoft. Expected dependency.	ai	2026/04/25
dependencies	unvetted-dep:@fluentui/react-shared-contexts	AI (dependencies): First-party @fluentui/* monorepo sibling package from Microsoft. Expected dependency.	ai	2026/04/25
bogus-package	bogus-package	AI (bogus-package): Short README and no keywords are typical of monorepo sub-packages; documentation lives in the root microsoft/fluentui repo. Not a spam/low-value indicator for this package.	ai	2026/04/25

Versions (showing 31 of 31)

Version	Deps	Published
9.5.2	8 / 0	2026-05-26
9.5.1	8 / 0	2026-04-23
9.5.0	8 / 0	2026-04-01
9.4.16	8 / 0	2026-03-11
9.4.15	8 / 0	2026-02-25
9.4.14	8 / 0	2026-02-12
9.4.13	8 / 0	2026-01-22
9.4.12	8 / 4	2025-12-17
9.4.11	8 / 4	2025-11-11
9.4.10	8 / 4	2025-11-06
9.4.9	8 / 4	2025-10-31
9.4.8	8 / 4	2025-10-21
9.4.7	8 / 4	2025-10-08
9.4.6	8 / 4	2025-10-02
9.4.5	8 / 4	2025-09-08
9.4.4	8 / 4	2025-08-21
9.4.3	8 / 4	2025-08-07
9.4.2	8 / 4	2025-07-30
9.4.1	8 / 4	2025-07-28
9.4.0	8 / 4	2025-07-17
9.3.7	8 / 4	2025-07-11
9.3.6	8 / 4	2025-07-04
9.3.5	8 / 4	2025-06-27
9.3.4	8 / 4	2025-06-26
9.3.3	8 / 4	2025-06-23
9.3.2	8 / 4	2025-06-18
9.3.1	8 / 4	2025-06-13
9.3.0	8 / 4	2025-06-12
9.2.9	8 / 4	2025-06-11
9.2.8	8 / 4	2025-06-06
9.2.7	8 / 4	2025-05-14

v9.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.1

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.4.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.4.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.4.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.4.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.4.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.4.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.