← Home

@ckeditor/ckeditor5-emoji

npm Repository Homepage

Emoji 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.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:build/emoji.js AI (source-diff): Standard webpack/rollup minified build output for CKEditor plugin; contains translation dictionaries and bundled CSS/JS. Not obfuscation. ai
phantom-deps phantom-dep:@ckeditor/ckeditor5-mention AI (phantom-deps): Same-org phantom dep is normal in CKEditor's monorepo architecture; mention plugin is a peer/indirect dependency. ai
provenance no-provenance AI (provenance): CKEditor packages do not currently publish with Sigstore provenance; stable for this package. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-typing AI (dependencies): First-party CKEditor 5 monorepo sibling package; unvetted status reflects pipeline lag, not a real risk. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-ui AI (dependencies): First-party CKEditor 5 monorepo sibling package; unvetted status reflects pipeline lag, not a real risk. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-mention AI (dependencies): First-party CKEditor 5 monorepo sibling package; unvetted status reflects pipeline lag, not a real risk. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-core AI (dependencies): First-party CKEditor 5 monorepo sibling package; unvetted status reflects pipeline lag, not a real risk. ai
dependencies unvetted-dep:@ckeditor/ckeditor5-utils AI (dependencies): First-party CKEditor 5 monorepo sibling package; unvetted status reflects pipeline lag, not a real risk. ai

Versions (showing 15 of 15)

Version Deps Published
48.2.0 8 / 0
48.1.1 8 / 0
48.1.0 8 / 0
48.0.1 8 / 0
48.0.0 8 / 0
47.7.2 9 / 0
47.7.1 9 / 0
47.7.0 9 / 0
47.6.2 9 / 0
47.6.1 9 / 0
47.6.0 9 / 0
47.5.0 9 / 0
47.4.0 9 / 0
47.3.0 9 / 0
47.2.0 9 / 0

v48.2.0

1 finding
INFO No provenance attestation provenance

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

v48.1.1

1 finding
INFO No provenance attestation provenance

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

v48.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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
INFO No provenance attestation provenance

[Accepted risk] 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/emoji.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

1 finding
LOW No provenance attestation provenance

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

v47.6.2

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.6.1

1 finding
INFO No provenance attestation provenance

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

v47.6.0

1 finding
INFO No provenance attestation provenance

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

v47.5.0

1 finding
INFO No provenance attestation provenance

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

v47.4.0

1 finding
INFO No provenance attestation provenance

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

v47.3.0

1 finding
INFO No provenance attestation provenance

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

v47.2.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.