← Home

@ckeditor/ckeditor5-pagination

npm Homepage

Pagination feature for CKEditor 5.

5
Versions
SEE LICENSE IN LICENSE.md
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ckeditor

Keywords

ckeditorckeditor5ckeditor 5ckeditor5-featureckeditor5-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ckeditor/ckeditor5-ui AI (dependencies): First-party CKEditor 5 package from the same org, released in lockstep at the same version. Not a third-party risk. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-core AI (dependencies): First-party CKEditor 5 package from the same org, released in lockstep at the same version. Not a third-party risk. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-utils AI (dependencies): First-party CKEditor 5 package from the same org, released in lockstep at the same version. Not a third-party risk. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-engine AI (dependencies): First-party CKEditor 5 package from the same org, released in lockstep at the same version. Not a third-party risk. ai
phantom-deps phantom-dep:@ckeditor/ckeditor5-icons AI (phantom-deps): Same-org CKEditor 5 package; used in compiled dist output. Expected pattern for this monorepo. ai

Versions (showing 5 of 5)

Version Deps Published
48.2.0 6 / 0
48.1.1 6 / 0
48.1.0 6 / 0
48.0.1 6 / 0
48.0.0 6 / 0

v48.2.0

1 finding
LOW No provenance attestation provenance

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

v48.1.1

1 finding
LOW No provenance attestation provenance

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

v48.1.0

1 finding
LOW No provenance attestation provenance

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

v48.0.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.

v48.0.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.