← Home

@swc-react/radio

npm Repository Homepage

React and Next.js wrapper of the @spectrum-web-components/radio component

18
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jnjoshtaratadoberajrock38nikkimkrubencjianliao79pvashishpatrickfultoncaseyisonit

Keywords

ReactSpectrum Web Components@spectrum-web-components/radio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:redis AI (typosquat): Package is an Adobe SWC React wrapper; name similarity to redis is purely coincidental edit-distance noise. ai
dependencies unvetted-dep:@spectrum-web-components/radio AI (dependencies): Expected upstream Adobe Spectrum Web Components dependency; stable for this package family. ai

Versions (showing 18 of 18)

Version Deps Published
1.11.2 2 / 0
1.11.1 2 / 0
1.11.0 2 / 0
1.10.0 2 / 0
1.9.1 2 / 0
1.9.0 2 / 0
1.8.0 2 / 0
1.7.0 2 / 0
1.6.0 2 / 0
1.5.0 2 / 0
1.4.0 2 / 0
1.3.0 2 / 0
1.2.0 2 / 0
1.1.2 2 / 0
1.1.1 2 / 0
1.0.3 2 / 0
1.0.1 2 / 0
1.0.0 2 / 0

v1.5.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: rubenc → rajrock38 (on 2025-04-15, known maintainer) provenance

This version was published by a different npm account (rajrock38) than the most recent previously approved version (rubenc) on 2025-04-15, but rajrock38 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: rajrock38 → rubenc (on 2025-02-27, known maintainer) provenance

This version was published by a different npm account (rubenc) than the most recent previously approved version (rajrock38) on 2025-02-27, but rubenc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.2

1 finding
LOW No provenance attestation provenance

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

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

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

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

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