@not-govuk/pagination
A component to help users navigate forwards and backwards through a series of pages.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all @not-govuk releases; no provenance is the norm for this publisher. | ai | |
| phantom-deps | phantom-dep:govuk-frontend | AI (phantom-deps): govuk-frontend is a SASS/CSS dependency referenced in config, not a JS import; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@not-govuk/sass-base | AI (phantom-deps): SASS-only dependency; not imported in JS, phantom-dep is a stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 6 / 6 | |
| 0.18.0 | 6 / 6 | |
| 0.17.4 | 6 / 6 | |
| 0.17.3 | 6 / 6 | |
| 0.17.2 | 6 / 6 | |
| 0.17.1 | 6 / 6 | |
| 0.17.0 | 6 / 6 | |
| 0.16.1 | 6 / 7 | |
| 0.15.14 | 6 / 7 |
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.16.1
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.