custom-classic-editor

v1.0.32

The classic editor build of CKEditor 5 – the best browser-based rich text editor. For more information about how to use this package see README

Latest version published 3 years ago
License: GPL-2.0-or-later

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

60 / 100

Security

Security review needed
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
1.0.32 | 11/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
GPL-2.0-or-later
Security Policy
Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (1)

Download trend
GitHub Stars
9.4K
Forks
3.69K
Contributors
160

Direct Usage Popularity


The npm package custom-classic-editor receives a total of 1 downloads a week. As such, we scored custom-classic-editor popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package custom-classic-editor, we found that it has been starred 9,399 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
160
Funding
Yes

A good and healthy external contribution signal for custom-classic-editor project, which invites more than one hundred open source maintainers to collaborate on the repository.

We found a way for you to contribute to the project! Looks like custom-classic-editor is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 60/100 package health 60/100

Maintenance

Inactive

Commit Frequency

Open Issues
1.29K
Open PR
61
Last Release
3 years ago
Last Commit
9 days ago

Further analysis of the maintenance status of custom-classic-editor based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for custom-classic-editor is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=12.0.0

Age
4 years
Dependencies
29 Direct
Versions
34
Install Size
10.1 MB
Dist-tags
1
# of Files
69
Maintainers
1
TS Typings
No

custom-classic-editor has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.