← Home

@react-stately/radio

npm Repository Homepage

Spectrum UI components in React

100
Versions
Apache-2.0
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

devongovettaspro83

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:redis AI (typosquat): @react-stately/radio is a scoped Adobe UI library package with no relation to redis; Levenshtein match is a false positive that will recur on every version. ai
phantom-deps phantom-dep:@swc/helpers AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled packages; standard pattern in Adobe's react-spectrum monorepo. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-packages commonly lack standalone README code blocks and keywords; not indicative of spam for this well-established Adobe package. ai

Versions (showing 100 of 198)

Hide prereleases
Version Deps Published
3.12.1 2 / 2
3.12.0 2 / 0
3.11.5 5 / 0
3.11.4 5 / 0
3.11.3 5 / 0
3.11.2 5 / 0
3.11.1 5 / 0
3.11.0 5 / 0
3.10.14 5 / 0
3.10.13 5 / 0
3.10.12 5 / 0
3.10.11 5 / 0
3.10.10 5 / 0
3.10.9 5 / 0
3.10.8 5 / 0
3.10.7 5 / 0
3.10.6 5 / 0
3.10.5 5 / 0
3.10.4 5 / 0
3.10.3 5 / 0
3.10.2 5 / 0
3.10.1 5 / 0
3.10.0 5 / 0
3.9.1 4 / 0
3.9.0 4 / 0
3.8.3 4 / 0
3.8.2 4 / 0
3.8.1 4 / 0
3.8.0 4 / 0
3.7.0 4 / 0
3.6.2 4 / 0
3.6.1 4 / 0
3.6.0 4 / 0
3.5.1 3 / 0
3.5.0 3 / 0
3.4.1 3 / 0
3.4.0 3 / 0
3.3.6 3 / 0
3.3.5 3 / 0
3.3.4 3 / 0
3.3.3 3 / 0
3.3.2 3 / 0
3.3.1 3 / 0
3.3.0 3 / 0
3.2.1 3 / 0
3.2.0 3 / 1
3.1.0 3 / 1
3.0.2 3 / 1
3.0.1 3 / 1
3.0.0 3 / 1
3.0.0-nightly-ffb1a9d0d-260323 2 / 0
3.0.0-nightly-ff8f6f319-251118 5 / 0
3.0.0-nightly-fc3ea3e8c-251029 5 / 0
3.0.0-nightly-f8d513f06-251119 5 / 0
3.0.0-nightly-f61e75cea-251124 5 / 0
3.0.0-nightly-f61e75cea-251123 5 / 0
3.0.0-nightly-f3e3157d0-260219 5 / 0
3.0.0-nightly-f3e3157d0-260218 5 / 0
3.0.0-nightly-f1aafc6ce-251105 5 / 0
3.0.0-nightly-efc581c91-260413 2 / 0
3.0.0-nightly-eef731921-260216 5 / 0
3.0.0-nightly-eef731921-260215 5 / 0
3.0.0-nightly-eef731921-260214 5 / 0
3.0.0-nightly-eec6c1a4d-251223 5 / 0
3.0.0-nightly-ee49fdbaf-260306 5 / 0
3.0.0-nightly-ec7736d18-260421 2 / 0
3.0.0-nightly-e3913baaa-260422 2 / 0
3.0.0-nightly-e24140214-260309 5 / 0
3.0.0-nightly-e24140214-260308 5 / 0
3.0.0-nightly-e24140214-260307 5 / 0
3.0.0-nightly-daafdd59d-260224 5 / 0
3.0.0-nightly-daafdd59d-260223 5 / 0
3.0.0-nightly-daafdd59d-260222 5 / 0
3.0.0-nightly-daafdd59d-260221 5 / 0
3.0.0-nightly-d974b93de-260227 5 / 0
3.0.0-nightly-cfb620016-260126 5 / 0
3.0.0-nightly-cfb620016-260125 5 / 0
3.0.0-nightly-cfb620016-260124 5 / 0
3.0.0-nightly-cf7c1541e-251113 5 / 0
3.0.0-nightly-cdbfe4816-260303 5 / 0
3.0.0-nightly-c8d64314e-260208 5 / 0
3.0.0-nightly-c8d64314e-260207 5 / 0
3.0.0-nightly-c80e3d1d6-251212 5 / 0
3.0.0-nightly-c5a3ae829-260331 2 / 0
3.0.0-nightly-c2517d3bb-260115 5 / 0
3.0.0-nightly-beda77877-260414 2 / 0
3.0.0-nightly-b4382b073-260130 5 / 0
3.0.0-nightly-b321d7de8-260122 5 / 0
3.0.0-nightly-b321d7de8-260121 5 / 0
3.0.0-nightly-ac718c6cd-260402 2 / 0
3.0.0-nightly-ab5e6f3db-251110 5 / 0
3.0.0-nightly-ab5e6f3db-251109 5 / 0
3.0.0-nightly-ab5e6f3db-251108 5 / 0
3.0.0-nightly-ab5e6f3db-251107 5 / 0
3.0.0-nightly-a9fccbde0-260302 5 / 0
3.0.0-nightly-a9fccbde0-260301 5 / 0
3.0.0-nightly-a9fccbde0-260228 5 / 0
3.0.0-nightly-a911b98f1-260325 2 / 0
3.0.0-nightly-a911b98f1-260324 2 / 0
3.0.0-nightly-a90e8f141-251218 5 / 0
Showing 100 of 198 Next page →

v3.12.1

1 finding
LOW No provenance attestation provenance

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

v3.12.0

1 finding
LOW No provenance attestation provenance

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

v3.11.5

1 finding
LOW No provenance attestation provenance

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

v3.11.4

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.

v3.11.3

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.

v3.11.2

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.

v3.11.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.

v3.11.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.

v3.10.14

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.

v3.10.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.

v3.10.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.

v3.10.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.

v3.10.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.

v3.10.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.

v3.10.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.

v3.10.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.

v3.10.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.

v3.10.5

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.

v3.10.4

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.

v3.10.3

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.

v3.10.2

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.

v3.10.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.

v3.10.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.

v3.9.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.

v3.9.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.

v3.8.3

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.

v3.8.2

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.

v3.8.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.

v3.8.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.

v3.7.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.

v3.6.2

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.

v3.6.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.

v3.6.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.

v3.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.

v3.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.

v3.4.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.

v3.4.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.

v3.3.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.

v3.3.5

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.

v3.3.4

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.

v3.3.3

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.

v3.3.2

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.

v3.3.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.

v3.3.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.

v3.2.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.

v3.2.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.

v3.1.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.

v3.0.2

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.

v3.0.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.

v3.0.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.