@radix-ui/react-select MIT 2 versions

@radix-ui/react-select

npm Repository Homepage

View docs [here](https://radix-ui.com/primitives/docs/components/select).

Versions

MIT

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

benoitgrelardstephenhaneyandy-hookhadihallakchancestricklandmark-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Radix UI primitives are component libs; short README and no keywords are normal for this org.	ai	2026/05/29
provenance	missing-githead	AI (provenance): Monorepo restructure dropped gitHead; publisher and package are well-established.	ai	2026/05/29
npm-metadata	no-description	AI (npm-metadata): Radix UI packages consistently omit descriptions; not indicative of malice.	ai	2026/04/29
provenance	no-provenance	AI (provenance): Radix UI primitives have never used Sigstore provenance; stable pattern for this publisher.	ai	2026/04/29

Versions (showing 2 of 2)

Version	Deps	Published
2.2.6	21 / 10	2025-08-13
2.1.6	21 / 9	2025-02-05

v2.2.6

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.

INFO No provenance attestation provenance

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

v2.1.6

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.