Gathering detailed insights and metrics for @ckeditor/ckeditor5-react
Gathering detailed insights and metrics for @ckeditor/ckeditor5-react
Gathering detailed insights and metrics for @ckeditor/ckeditor5-react
Gathering detailed insights and metrics for @ckeditor/ckeditor5-react
@mdfe/ckeditor5-react
Official React component for CKEditor 5 – the best browser-based rich text editor.
@tony/ckeditor5-fileupload-react
A plugin for CKEditor 5.
anhnk3-ckeditor5
CKEditor 5 Classic Plus is a custom build built on top of CKEditor 5 Build - Classic (version: 35.0.1). It adds Simple Upload Adapter, Image Resize, Font Styling and much more to the official build.
ronds-react-markdown
React Ckeditor 5 for markdown
Official CKEditor 5 React component.
npm install @ckeditor/ckeditor5-react
Typescript
Module System
Min. Node Version
Node Version
NPM Version
95.6
Supply Chain
96.2
Quality
87.5
Maintenance
100
Vulnerability
50
License
TypeScript (94.81%)
JavaScript (4.88%)
HTML (0.22%)
Shell (0.09%)
Total Downloads
27,730,978
Last Day
16,851
Last Week
266,919
Last Month
1,132,853
Last Year
11,155,192
NOASSERTION License
446 Stars
843 Commits
102 Forks
19 Watchers
13 Branches
64 Contributors
Updated on May 26, 2025
Minified
Minified + Gzipped
Latest Version
9.5.0
Package Id
@ckeditor/ckeditor5-react@9.5.0
Unpacked Size
416.51 kB
Size
95.57 kB
File Count
29
NPM Version
10.9.0
Node Version
22.11.0
Published on
Feb 13, 2025
Cumulative downloads
Total Downloads
Last Day
8.6%
16,851
Compared to previous day
Last Week
-2.9%
266,919
Compared to previous week
Last Month
6.3%
1,132,853
Compared to previous month
Last Year
72.3%
11,155,192
Compared to previous year
1
Official CKEditor 5 rich text editor component for React.
See the "Rich text editor component for React" guide in the CKEditor 5 documentation to learn more:
After cloning this repository, install necessary dependencies:
1npm install
You can also use Yarn.
To manually test the editor integration with different versions of React, you can start the development server using one of the commands below:
1npm run dev:16 # Open the demo projects using React 16. 2npm run dev:18 # Open the demo projects using React 18. 3npm run dev:19 # Open the demo projects using React 19.
To test the editor integration against a set of automated tests, run the following command:
1npm run test
If you want to run the tests in watch mode, use the following command:
1npm run test:watch
To build the package that is ready to publish, use the following command:
1npm run build
CircleCI automates the release process and can release both channels: stable (X.Y.Z
) and pre-releases (X.Y.Z-alpha.X
, etc.).
Before you start, you need to prepare the changelog entries.
#master
branch is up-to-date: git fetch && git checkout master && git pull
.git checkout -b release-[YYYYMMDD]
where YYYYMMDD
is the current day.yarn run changelog --branch release-[YYYYMMDD] [--from [GIT_TAG]]
.
By default, the changelog generator uses the latest published tag as a starting point for collecting commits to process.
The --from
modifier option allows overriding the default behavior. It is required when preparing the changelog entries for the next stable release while the previous one was marked as a prerelease, e.g., @alpha
.
Example: Let's assume that the v40.5.0-alpha.0
tag is our latest and that we want to release it on a stable channel. The --from
modifier should be equal to --from v40.4.0
.
This task checks what changed in each package and bumps the version accordingly. It won't create a new changelog entry if nothing changes at all. If changes were irrelevant (e.g., only dependencies), it would make an "internal changes" entry.
Scan the logs printed by the tool to search for errors (incorrect changelog entries). Incorrect entries (e.g., ones without the type) should be addressed. You may need to create entries for them manually. This is done directly in CHANGELOG.md (in the root directory). Make sure to verify the proposed version after you modify the changelog.
#master
branch.@ckeditor/ckeditor-5-devops
team to review the pull request and trigger the release process.Licensed under a dual-license model, this software is available under:
For more information, see: https://ckeditor.com/legal/ckeditor-licensing-options.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
Found 7/8 approved changesets -- score normalized to 8
Reason
3 existing vulnerabilities detected
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Score
Last Scanned on 2025-05-26
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More