@not-govuk/select
A component to allow users to choose from many 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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @not-govuk/* packages; org does not use Sigstore attestation. | ai | |
| phantom-deps | phantom-dep:@not-govuk/sass-base | AI (phantom-deps): SCSS-only dep; not imported in JS but used via sass entry point — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:govuk-frontend | AI (phantom-deps): Referenced in SCSS/config, not JS imports — expected pattern for GOV.UK frontend styling deps. | ai |
Versions (showing 64 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 4 / 6 | |
| 0.18.0 | 4 / 6 | |
| 0.17.4 | 4 / 6 | |
| 0.17.3 | 4 / 6 | |
| 0.17.2 | 4 / 6 | |
| 0.17.1 | 4 / 6 | |
| 0.17.0 | 4 / 6 | |
| 0.16.3 | 4 / 7 | |
| 0.16.2 | 4 / 7 | |
| 0.16.1 | 4 / 7 | |
| 0.16.0 | 4 / 7 | |
| 0.15.14 | 4 / 7 | |
| 0.15.12 | 4 / 7 | |
| 0.15.11 | 4 / 7 | |
| 0.15.10 | 4 / 7 | |
| 0.15.9 | 4 / 7 | |
| 0.15.8 | 4 / 7 | |
| 0.15.7 | 4 / 7 | |
| 0.15.6 | 4 / 7 | |
| 0.15.5 | 4 / 7 | |
| 0.15.4 | 4 / 7 | |
| 0.15.3 | 4 / 7 | |
| 0.15.2 | 4 / 7 | |
| 0.15.1 | 4 / 7 | |
| 0.15.0 | 4 / 7 | |
| 0.14.0 | 4 / 7 | |
| 0.13.0 | 4 / 7 | |
| 0.12.1 | 4 / 7 | |
| 0.12.0 | 4 / 7 | |
| 0.11.1 | 4 / 7 | |
| 0.11.0 | 4 / 7 | |
| 0.10.0 | 4 / 7 | |
| 0.9.1 | 4 / 7 | |
| 0.9.0 | 4 / 7 | |
| 0.8.7 | 4 / 7 | |
| 0.8.6 | 4 / 7 | |
| 0.8.5 | 4 / 7 | |
| 0.8.4 | 4 / 7 | |
| 0.8.3 | 4 / 7 | |
| 0.8.2 | 4 / 7 | |
| 0.8.1 | 4 / 7 | |
| 0.8.0 | 4 / 7 | |
| 0.7.2 | 4 / 7 | |
| 0.7.1 | 4 / 7 | |
| 0.7.0 | 4 / 7 | |
| 0.6.0 | 4 / 7 | |
| 0.5.9 | 4 / 7 | |
| 0.5.8 | 4 / 7 | |
| 0.5.7 | 4 / 7 | |
| 0.5.6 | 4 / 7 | |
| 0.5.5 | 4 / 7 | |
| 0.5.4 | 4 / 7 | |
| 0.5.3 | 4 / 7 | |
| 0.5.2 | 4 / 7 | |
| 0.5.1 | 4 / 7 | |
| 0.5.0 | 4 / 7 | |
| 0.4.2 | 4 / 6 | |
| 0.4.1 | 4 / 6 | |
| 0.4.0 | 4 / 6 | |
| 0.3.4 | 4 / 6 | |
| 0.3.3 | 4 / 6 | |
| 0.3.2 | 4 / 6 | |
| 0.3.1 | 4 / 6 | |
| 0.3.0 | 4 / 6 |
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.