← Home

@instructure/ui-radio-input

A styled HTML input type='radio' element

15
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

jakeoedinginstuicimaths22jcrystalitadminsaogata-instpkovaacskyler-instructureericsaupexcudderjdewarjozsefg-instructurejacksonhowekaroly.bujtor.instructureevatapaisarahgerardkercsojforbidwolfbencefarkasodmehbvikingpingvinajmal-esarobinkuss64david.wenzlick.instrazorsh4rkardenabpjatacsukangela.gombanatearmstronginstjoyenjoyercguanzon-instherrtopimatyas.szabocjs118camraydmz985kristofkulcsarinstructure-npm-write-svc-accountmhulse_instsvetlintanyimhogensonppesti-instaaronshafszilard.doro-instmartongreczi-instinstoutsvcquizzesnpmbalazs.buri.instructuredaniel-torokfmarcsopeipeizhouis-adamszaborajmund-instdanny-instructure

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA attestation present; gitHead absence is a minor metadata gap, not a supply chain risk for this well-established monorepo package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are within the same Instructure org; routine team rotation. ai
provenance publisher-changed AI (provenance): Instructure monorepo publishes via GitHub Actions CI/CD with SLSA attestation; this is the expected pattern. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal paired with additions within same org; consistent with team rotation, not takeover. ai
publish-pattern new-deps-added AI (publish-pattern): New deps are pinned same-version Instructure monorepo packages and prop-types; consistent with coordinated monorepo releases. ai
dependencies unvetted-dep:@instructure/ui-prop-types AI (dependencies): Same-monorepo sibling dep pinned to matching version; standard Instructure UI release pattern. ai
dependencies unvetted-dep:@instructure/ui-testable AI (dependencies): Same-monorepo sibling dep pinned to matching version; standard Instructure UI release pattern. ai
dependencies unvetted-dep:@instructure/emotion AI (dependencies): Sibling monorepo package; versioned in lockstep with this package across all releases. ai
dependencies unvetted-dep:@instructure/ui-react-utils AI (dependencies): Sibling monorepo package; versioned in lockstep with this package across all releases. ai
dependencies unvetted-dep:@instructure/ui-form-field AI (dependencies): Sibling monorepo package; versioned in lockstep with this package across all releases. ai
dependencies unvetted-dep:@instructure/ui-a11y-utils AI (dependencies): Sibling monorepo package; versioned in lockstep with this package across all releases. ai

Versions (showing 15 of 15)

Version Deps Published
11.7.3 8 / 7
11.7.2 7 / 8
11.7.1 7 / 8
11.7.0 7 / 8
11.6.0 7 / 8
11.5.0 7 / 8
11.4.0 7 / 8
11.3.0 7 / 8
11.2.0 7 / 8
11.0.1 6 / 8
11.0.0 6 / 8
10.30.0 9 / 8
10.29.0 9 / 8
10.26.4 9 / 8
10.26.3 9 / 8

v11.7.3

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: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.7.1

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-03-20) provenance

This version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.7.0

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-03-18) provenance

This version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.6.0

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-02-18) provenance

This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.5.0

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-02-03) provenance

This version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.4.0

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-01-20) provenance

This version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.0

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-01-12) provenance

This version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

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

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

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

v10.30.0

2 findings
HIGH Publisher changed: matyas.szabo → GitHub Actions (on 2026-02-20) provenance

This version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.29.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v10.26.4

1 finding
LOW No provenance attestation provenance

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

v10.26.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.