ckeditor5-build-spo

GPL-2.0-or-laterLicense declared in the package manifest.

The classic editor build of CKEditor 5 – the best browser-based rich text editor.

ckeditor5-buildckeditorckeditor5ckeditor 5wysiwygrich texteditorhtml
73

Security score

0 known advisories in v29.2.1

OpenSSF Scorecard 4.6/10

0-100 score computed by this site from verifiable signals only: known OSV.dev advisories affecting this exact version, how recently it was published, and the repository's OpenSSF Scorecard.advisory penalty −0 · staleness penalty −15 · scorecard component 46/100 (30% weight)

Weekly downloads

Downloads across all versions in the last 7 days, from the official npm downloads API (api.npmjs.org).

—

Unpacked size

Size of v29.2.1 on disk after npm install extracts the tarball, as reported by the npm registry.

5.9 MB

Dependencies

Direct runtime dependencies declared by v29.2.1. Transitive dependencies are not counted here — use the lockfile audit for the full tree.

19

Last publish

When v29.2.1 was published to the registry. Long gaps can indicate an unmaintained package.

4 years ago

Security advisories

Vulnerabilities affecting v29.2.1 specifically, from OSV.dev — the open database aggregating the GitHub Advisory Database (GHSA) and CVEs. Links open the full advisory.

No known vulnerabilities affect v29.2.1.

OpenSSF ScorecardAug 3, 2026

OpenSSF Scorecard is an automated audit of the source repository's security practices, run by the Open Source Security Foundation. Each check scores 0-10; hover a check for what it means. Data via deps.dev.
  • MaintainedThe project shows recent activity: commits or issue triage within the last 90 days.Result: 30 commit(s) and 24 issue activity found in the last 90 days -- score normalized to 1010
  • Code-ReviewChanges are reviewed by another maintainer before landing on the main branch.Result: Found 0/30 approved changesets -- score normalized to 00
  • Security-PolicyA SECURITY.md explains how to report vulnerabilities privately.Result: security policy file detected10
  • CII-Best-PracticesThe project holds an OpenSSF Best Practices badge, a self-certification of security practices.Result: no effort to earn an OpenSSF best practices badge detected0
  • LicenseThe project publishes a license file.Result: license file detected9
  • SASTStatic analysis (e.g. CodeQL) runs on pull requests to catch bugs before merge.Result: no SAST tool detected0
  • Branch-ProtectionThe default branch is protected: force pushes are blocked and changes require review before merging.Result: branch protection is not maximal on development and all release branches1
  • Binary-ArtifactsNo compiled binaries are committed to the repository — binaries can't be reviewed and may hide malicious code.Result: no binaries found in the repo10
  • FuzzingThe project is fuzz-tested (e.g. OSS-Fuzz), which finds crashes and memory bugs automatically.Result: project is not fuzzed0