← Home

@not-govuk/summary-list

npm

A component to summarise information, for example, a user’s responses at the end of a form.

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

daniel-ac-martin

Keywords

react-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 8 of 8)

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.15.14 5 / 9

v0.18.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.

v0.18.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.

v0.17.4

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.

v0.17.3

1 finding
LOW No provenance attestation provenance

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

v0.17.2

1 finding
LOW No provenance attestation provenance

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

v0.17.1

1 finding
LOW No provenance attestation provenance

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

v0.17.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.

v0.15.14

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.