@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, 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@not-govuk/uri | AI (dependencies): Same-org sibling package in the not-govuk monorepo, not third-party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Internal org dependency swap, not an unrelated third-party addition. | ai | |
| 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 43 of 43)
| 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.16.0 | 6 / 7 | |
| 0.15.14 | 6 / 7 | |
| 0.15.12 | 6 / 7 | |
| 0.15.11 | 6 / 7 | |
| 0.15.10 | 6 / 7 | |
| 0.15.9 | 6 / 7 | |
| 0.15.8 | 6 / 7 | |
| 0.15.7 | 6 / 7 | |
| 0.15.6 | 6 / 7 | |
| 0.15.4 | 6 / 7 | |
| 0.15.3 | 6 / 7 | |
| 0.15.2 | 6 / 7 | |
| 0.15.1 | 6 / 7 | |
| 0.15.0 | 6 / 7 | |
| 0.14.0 | 6 / 7 | |
| 0.13.0 | 6 / 7 | |
| 0.12.1 | 6 / 7 | |
| 0.12.0 | 6 / 7 | |
| 0.11.1 | 6 / 7 | |
| 0.11.0 | 6 / 7 | |
| 0.10.0 | 6 / 7 | |
| 0.9.1 | 6 / 7 | |
| 0.9.0 | 6 / 7 | |
| 0.8.7 | 6 / 7 | |
| 0.8.6 | 6 / 7 | |
| 0.8.5 | 6 / 7 | |
| 0.8.4 | 6 / 7 | |
| 0.8.3 | 6 / 7 | |
| 0.8.2 | 6 / 7 | |
| 0.8.1 | 6 / 7 | |
| 0.8.0 | 6 / 7 | |
| 0.7.2 | 6 / 7 | |
| 0.7.1 | 6 / 7 | |
| 0.7.0 | 6 / 7 | |
| 0.6.0 | 6 / 7 |
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.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.