Is Ckeditor5 Safe?

Ckeditor5 — Nerq Trust Score 66.5/100 (B- grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-20

Ckeditor5 is a npm package with a Nerq Trust Score of 66.5/100 (B-), based on 3 independent data dimensions. Last analyzed: 2026-03-20 Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-20. Machine-readable data (JSON).

Is Ckeditor5 safe?

Trust Score Breakdown — Ckeditor5 has a Nerq Trust Score of 66.5/100 (B-). Measured across 2 independent trust signals (as of 2026-03-20).

Security Analysis → Ckeditor5 Privacy Report →

What is Ckeditor5's trust score?

Ckeditor5 has a Nerq Trust Score of 66.5/100, earning a B- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Ckeditor5?

Ckeditor5's strongest signal is security at 90/100. No known vulnerabilities have been detected.

Security score: 90/100 (strong)
Popularity: 0/100 — community adoption

What is Ckeditor5 and who maintains it?

Authorckeditor
Categorynpm Packages
SourceN/A

Ckeditor5 Across Platforms

Same developer/company in other registries:

ckeditor/ckeditor
52/100 · packagist

Similar Npm by Trust Score

@smithy/is-array-buffer (76)@marko/vite (76)@okta/okta-signin-widget (76)@ag-ui/encoder (76)@ui5/server (76)
See all safest Npm →

Compare

Ckeditor5 vs @smithy/is-array-bufferCkeditor5 vs @marko/viteCkeditor5 vs @okta/okta-signin-widget

Safety Guide: Ckeditor5

What is Ckeditor5?

Ckeditor5 is a Node.js package — A set of ready-to-use rich text editors created with a powerful framework. Made with real-time collaborative editing in mind..

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=ckeditor5

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Measured Signals

Ckeditor5 has a Nerq Trust Score of 66/100 (B-). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Ckeditor5 Safe?
ckeditor5 with a Nerq Trust Score of 66.5/100 (B-). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Ckeditor5's trust score?
ckeditor5: 66.5/100 (B-). Score based on Security (90/100), Popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=ckeditor5
What are safer alternatives to Ckeditor5?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. ckeditor5 scores 66.5/100.
Does Ckeditor5 have known vulnerabilities?
Nerq checks Ckeditor5 against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Ckeditor5 actively maintained?
Ckeditor5 maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy