@not-govuk/cookie-banner
A component to allow users to accept or reject cookies which are not essential to making your service work.
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 versions of this org's packages; not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:@not-govuk/sass-base | AI (phantom-deps): Same-org SCSS dependency; referenced in SASS assets, not JS imports. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:govuk-frontend | AI (phantom-deps): govuk-frontend is a SCSS/asset dependency referenced in config/SASS files, not JS imports. Expected pattern for this package. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 5 / 9 | |
| 0.18.0 | 5 / 9 | |
| 0.17.4 | 5 / 9 | |
| 0.17.3 | 5 / 9 | |
| 0.17.2 | 5 / 9 | |
| 0.17.1 | 5 / 9 | |
| 0.17.0 | 5 / 9 | |
| 0.16.0 | 5 / 10 | |
| 0.15.14 | 5 / 10 | |
| 0.15.12 | 5 / 10 | |
| 0.15.11 | 5 / 10 | |
| 0.15.10 | 5 / 10 | |
| 0.15.9 | 5 / 10 | |
| 0.15.8 | 5 / 10 | |
| 0.15.7 | 5 / 10 | |
| 0.15.6 | 5 / 10 | |
| 0.15.5 | 5 / 10 | |
| 0.15.4 | 5 / 10 | |
| 0.15.3 | 5 / 10 | |
| 0.15.2 | 5 / 10 | |
| 0.15.1 | 5 / 10 | |
| 0.15.0 | 5 / 10 | |
| 0.14.0 | 5 / 10 | |
| 0.13.0 | 5 / 10 | |
| 0.12.1 | 5 / 10 | |
| 0.12.0 | 5 / 10 | |
| 0.11.1 | 5 / 10 | |
| 0.11.0 | 5 / 10 | |
| 0.10.0 | 5 / 10 | |
| 0.9.1 | 5 / 10 | |
| 0.9.0 | 5 / 10 | |
| 0.8.7 | 5 / 10 | |
| 0.8.6 | 5 / 10 | |
| 0.8.5 | 5 / 10 | |
| 0.8.4 | 5 / 10 | |
| 0.8.3 | 5 / 10 | |
| 0.8.2 | 5 / 10 | |
| 0.8.1 | 5 / 10 | |
| 0.8.0 | 5 / 10 | |
| 0.7.2 | 5 / 10 | |
| 0.7.1 | 5 / 10 | |
| 0.7.0 | 5 / 10 | |
| 0.6.0 | 5 / 10 | |
| 0.5.9 | 5 / 10 | |
| 0.5.8 | 5 / 10 | |
| 0.5.7 | 5 / 10 | |
| 0.5.6 | 5 / 10 | |
| 0.5.5 | 5 / 10 | |
| 0.5.4 | 5 / 10 | |
| 0.5.3 | 5 / 10 | |
| 0.5.2 | 5 / 10 | |
| 0.5.1 | 5 / 10 | |
| 0.5.0 | 5 / 10 | |
| 0.4.2 | 5 / 9 | |
| 0.4.1 | 5 / 9 | |
| 0.4.0 | 5 / 9 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.