@ckeditor/ckeditor5-mention
Mention feature for CKEditor 5.
18
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, so a manually published version cannot be tied back to a reviewed commit.
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/mention.js | AI (source-diff): Standard webpack/bundler output for CKEditor plugin; contains CSS loaders and style definitions, not malicious obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): CKEditor5 is a large established monorepo publisher; lack of Sigstore provenance is consistent across all their releases and not a meaningful risk signal. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): CKEditor5 uses a standard dual commercial/open-source license referenced via LICENSE.md; this is consistent across all @ckeditor/* packages. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 48.3.1 | 6 / 0 | |
| 48.3.0 | 6 / 0 | |
| 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 | |
| 47.7.3 | 6 / 0 | |
| 47.7.2 | 6 / 0 | |
| 47.7.1 | 6 / 0 | |
| 47.7.0 | 6 / 0 | |
| 47.6.2 | 6 / 0 | |
| 47.6.1 | 6 / 0 | |
| 47.6.0 | 6 / 0 | |
| 47.5.0 | 6 / 0 | |
| 47.4.0 | 6 / 0 | |
| 47.3.0 | 6 / 0 | |
| 47.2.0 | 6 / 0 |
v48.3.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.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.7.3
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.