@not-govuk/radios
A component to allow users to choose between a small selection of options.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:axios | AI (typosquat): Scoped @not-govuk/* component library; no relation to axios. | ai | |
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Scoped @not-govuk/* component library; no relation to redis. | ai | |
| phantom-deps | phantom-dep:govuk-frontend | AI (phantom-deps): govuk-frontend is a SCSS/asset dependency, not a JS import; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:@not-govuk/sass-base | AI (phantom-deps): SCSS-only dependency from same org scope; not imported as JS. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 6 / 7 | |
| 0.18.0 | 6 / 7 | |
| 0.17.4 | 6 / 7 | |
| 0.17.3 | 6 / 7 | |
| 0.17.2 | 6 / 7 | |
| 0.17.1 | 6 / 7 | |
| 0.17.0 | 6 / 7 | |
| 0.15.14 | 6 / 8 |
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.