← Home

@react-spectrum/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-spectrum/radio is an official Adobe React Spectrum scoped package with no plausible confusion with 'redis'. Levenshtein match is a false positive for this well-established package. ai
phantom-deps phantom-dep:@swc/helpers AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled packages; its presence is expected and stable across all versions of this package. ai
bogus-package bogus-package AI (bogus-package): Short README and no keywords are typical for monorepo sub-packages in the adobe/react-spectrum repo; not indicative of spam or low-value content. ai

Versions (showing 100 of 205)

Hide prereleases
Version Deps Published
3.8.1 2 / 2
3.8.0 2 / 0
3.7.24 10 / 1
3.7.23 10 / 1
3.7.22 10 / 1
3.7.21 10 / 1
3.7.20 10 / 1
3.7.19 10 / 1
3.7.18 10 / 1
3.7.17 10 / 1
3.7.16 10 / 1
3.7.15 10 / 1
3.7.14 10 / 1
3.7.13 10 / 1
3.7.12 10 / 1
3.7.11 10 / 1
3.7.10 10 / 1
3.7.9 10 / 1
3.7.8 10 / 1
3.7.7 10 / 1
3.7.6 10 / 1
3.7.5 10 / 1
3.7.4 10 / 1
3.7.3 10 / 1
3.7.2 10 / 1
3.7.1 10 / 1
3.7.0 10 / 1
3.6.2 10 / 1
3.6.1 10 / 1
3.6.0 10 / 1
3.5.4 10 / 1
3.5.3 10 / 1
3.5.2 10 / 1
3.5.1 10 / 1
3.5.0 10 / 1
3.4.3 10 / 1
3.4.2 10 / 1
3.4.1 10 / 1
3.4.0 10 / 1
3.3.1 10 / 1
3.3.0 10 / 1
3.2.1 10 / 1
3.2.0 10 / 1
3.1.10 10 / 1
3.1.9 10 / 1
3.1.8 10 / 1
3.1.7 10 / 1
3.1.6 10 / 1
3.1.5 10 / 1
3.1.4 10 / 1
3.1.3 10 / 1
3.1.2 10 / 1
3.1.1 10 / 1
3.1.0 10 / 1
3.0.2 9 / 1
3.0.1 9 / 1
3.0.0 9 / 1
3.0.0-nightly-ffb1a9d0d-260323 2 / 0
3.0.0-nightly-ff8f6f319-251118 10 / 1
3.0.0-nightly-fc3ea3e8c-251029 10 / 1
3.0.0-nightly-f8d513f06-251119 10 / 1
3.0.0-nightly-f61e75cea-251124 10 / 1
3.0.0-nightly-f61e75cea-251123 10 / 1
3.0.0-nightly-f3e3157d0-260219 10 / 1
3.0.0-nightly-f3e3157d0-260218 10 / 1
3.0.0-nightly-f1aafc6ce-251105 10 / 1
3.0.0-nightly-efc581c91-260413 2 / 0
3.0.0-nightly-eef731921-260216 10 / 1
3.0.0-nightly-eef731921-260215 10 / 1
3.0.0-nightly-eef731921-260214 10 / 1
3.0.0-nightly-eec6c1a4d-251223 10 / 1
3.0.0-nightly-ee49fdbaf-260306 10 / 1
3.0.0-nightly-ec7736d18-260421 2 / 0
3.0.0-nightly-e3913baaa-260422 2 / 0
3.0.0-nightly-e24140214-260309 10 / 1
3.0.0-nightly-e24140214-260308 10 / 1
3.0.0-nightly-e24140214-260307 10 / 1
3.0.0-nightly-daafdd59d-260224 10 / 1
3.0.0-nightly-daafdd59d-260223 10 / 1
3.0.0-nightly-daafdd59d-260222 10 / 1
3.0.0-nightly-daafdd59d-260221 10 / 1
3.0.0-nightly-d974b93de-260227 10 / 1
3.0.0-nightly-cfb620016-260126 10 / 1
3.0.0-nightly-cfb620016-260125 10 / 1
3.0.0-nightly-cfb620016-260124 10 / 1
3.0.0-nightly-cf7c1541e-251113 10 / 1
3.0.0-nightly-cdbfe4816-260303 10 / 1
3.0.0-nightly-c8d64314e-260208 10 / 1
3.0.0-nightly-c8d64314e-260207 10 / 1
3.0.0-nightly-c80e3d1d6-251212 10 / 1
3.0.0-nightly-c5a3ae829-260331 2 / 0
3.0.0-nightly-c2517d3bb-260115 10 / 1
3.0.0-nightly-beda77877-260414 2 / 0
3.0.0-nightly-b4382b073-260130 10 / 1
3.0.0-nightly-b321d7de8-260122 10 / 1
3.0.0-nightly-b321d7de8-260121 10 / 1
3.0.0-nightly-ac718c6cd-260402 2 / 0
3.0.0-nightly-ab5e6f3db-251110 10 / 1
3.0.0-nightly-ab5e6f3db-251109 10 / 1
3.0.0-nightly-ab5e6f3db-251108 10 / 1
Showing 100 of 205 Next page →

v3.8.1

1 finding
LOW No provenance attestation provenance

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

v3.8.0

1 finding
LOW No provenance attestation provenance

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

v3.7.24

1 finding
LOW No provenance attestation provenance

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

v3.7.23

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

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

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

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

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

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

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

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

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.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.7.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.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.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.5.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.5.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.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.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.4.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.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.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.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.1.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.1.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.1.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.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.

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