@ckeditor/ckeditor5-bookmark SEE LICENSE IN LICENSE.md 15 versions

@ckeditor/ckeditor5-bookmark

npm Repository Homepage

Bookmark feature for CKEditor 5.

15

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.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:build/bookmark.js	AI (source-diff): Standard minified build bundle for CKEditor 5 package; contains translations and CSS, not obfuscation. Stable for this package.	ai	2026/04/26
source-diff	large-new-source-files	AI (source-diff): CKEditor packages ship build/ and dist/ directories with pre-built bundles; large file counts are expected.	ai	2026/04/26
phantom-deps	phantom-dep:@ckeditor/ckeditor5-link	AI (phantom-deps): Sibling monorepo dep declared but not directly imported; consistent with CKEditor5 monorepo structure where deps may be re-exported or transitively used.	ai	2026/04/25
phantom-deps	phantom-dep:@ckeditor/ckeditor5-typing	AI (phantom-deps): Sibling monorepo dep declared but not directly imported; consistent with CKEditor5 monorepo structure where deps may be re-exported or transitively used.	ai	2026/04/25

Versions (showing 15 of 15)

Version	Deps	Published
48.2.0	8 / 0	2026-06-02
48.1.1	8 / 0	2026-05-18
48.1.0	8 / 0	2026-05-13
48.0.1	8 / 0	2026-04-22
48.0.0	8 / 0	2026-03-31
47.7.2	7 / 0	2026-05-18
47.7.1	7 / 0	2026-04-23
47.7.0	7 / 0	2026-04-16
47.6.2	7 / 0	2026-04-08
47.6.1	7 / 0	2026-03-11
47.6.0	7 / 0	2026-03-04
47.5.0	7 / 0	2026-02-11
47.4.0	7 / 0	2026-01-14
47.3.0	7 / 0	2025-12-03
47.2.0	7 / 0	2025-11-05

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.

v47.7.2

1 finding

LOW No provenance attestation provenance

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

v47.7.1

2 findings

HIGH New obfuscated file: build/bookmark.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v47.7.0

2 findings

HIGH New obfuscated file: build/bookmark.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v47.6.2

2 findings

HIGH New obfuscated file: build/bookmark.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v47.6.1

1 finding

LOW No provenance attestation provenance

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

v47.6.0

1 finding

LOW No provenance attestation provenance

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

v47.5.0

1 finding

LOW No provenance attestation provenance

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

v47.4.0

1 finding

LOW No provenance attestation provenance

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

v47.3.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.

v47.2.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.