@not-govuk/summary-list
A component to summarise information, for example, a user’s responses at the end of a form.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@not-govuk/sass-base | AI (phantom-deps): Same org scope SCSS dependency; not directly imported in JS but legitimately declared for SASS consumers. | ai | |
| phantom-deps | phantom-dep:govuk-frontend | AI (phantom-deps): govuk-frontend is a SCSS/asset dependency referenced in config, not a JS import; phantom-dep is a stable false positive here. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 5 / 8 | |
| 0.18.0 | 5 / 8 | |
| 0.17.4 | 5 / 8 | |
| 0.17.3 | 5 / 8 | |
| 0.17.2 | 5 / 8 | |
| 0.17.1 | 5 / 8 | |
| 0.17.0 | 5 / 8 | |
| 0.16.3 | 5 / 9 | |
| 0.16.2 | 5 / 9 | |
| 0.16.1 | 5 / 9 | |
| 0.16.0 | 5 / 9 | |
| 0.15.14 | 5 / 9 | |
| 0.15.12 | 5 / 9 | |
| 0.15.11 | 5 / 9 | |
| 0.15.10 | 5 / 9 | |
| 0.15.9 | 5 / 9 | |
| 0.15.8 | 5 / 9 | |
| 0.15.7 | 5 / 9 | |
| 0.15.6 | 5 / 9 | |
| 0.15.5 | 5 / 9 | |
| 0.15.4 | 5 / 9 | |
| 0.15.3 | 5 / 9 | |
| 0.15.2 | 5 / 9 | |
| 0.15.1 | 5 / 9 | |
| 0.15.0 | 5 / 9 | |
| 0.14.0 | 5 / 9 | |
| 0.13.0 | 5 / 9 | |
| 0.12.1 | 5 / 9 | |
| 0.12.0 | 5 / 9 | |
| 0.11.1 | 5 / 9 | |
| 0.11.0 | 5 / 9 | |
| 0.10.0 | 5 / 9 | |
| 0.9.1 | 5 / 9 | |
| 0.9.0 | 5 / 9 | |
| 0.8.7 | 5 / 9 | |
| 0.8.6 | 5 / 9 | |
| 0.8.5 | 5 / 9 | |
| 0.8.4 | 5 / 9 | |
| 0.8.3 | 5 / 9 | |
| 0.8.2 | 5 / 9 | |
| 0.8.1 | 5 / 9 | |
| 0.8.0 | 5 / 9 |
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.