testing_blog_1

v32.0.0

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

NPM

GitHub

Package Health Score

63 / 100

security
No known security issues
popularity
Small
maintenance
Inactive
community
Active

Explore Similar Packages

Security

No known security issues

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
32.0.0	\|	04/2022	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 (2)

GitHub Stars: 9.45K
Forks: 3.69K
Contributors: 160

Direct Usage Popularity

The npm package testing_blog_1 receives a total of 2 downloads a week. As such, we scored testing_blog_1 popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package testing_blog_1, we found that it has been starred 9,446 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 testing_blog_1 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 testing_blog_1 is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 1.25K
Open PR: 60
Last Release: 3 years ago
Last Commit: 2 months ago

Further analysis of the maintenance status of testing_blog_1 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 testing_blog_1 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=14.0.0

Age: 3 years
Dependencies: 21 Direct
Versions: 2
Install Size: 6.76 MB
Dist-tags: 1
# of Files: 71
Maintainers: 1
TS Typings: No

testing_blog_1 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.

Readme

CKEditor 5 classic editor build

The classic editor build for CKEditor 5. Read more about the classic editor build and see the demo.

CKEditor 5 classic editor build screenshot

Documentation

See:

Installation for how to install this package and what it contains.
Basic API for how to create an editor and interact with it.
Configuration for how to configure the editor.
Creating custom builds for how to customize the build (configure and rebuild the editor bundle).

Quick start

First, install the build from npm:

npm install --save @ckeditor/ckeditor5-build-classic

And use it in your website:

<div id="editor">
	<p>This is the editor content.</p>
</div>

Or in your JavaScript application:

import ClassicEditor from '@ckeditor/ckeditor5-build-classic';

// Or using the CommonJS version:
// const ClassicEditor = require( '@ckeditor/ckeditor5-build-classic' );

ClassicEditor
	.create( document.querySelector( '#editor' ) )
	.then( editor =&gt; {
		window.editor = editor;
	} )
	.catch( error =&gt; {
		console.error( 'There was a problem initializing the editor.', error );
	} );

Note: If you are planning to integrate CKEditor 5 deep into your application, it is actually more convenient and recommended to install and import the source modules directly (like it happens in ckeditor.js). Read more in the Advanced setup guide.

License

Licensed under the terms of GNU General Public License Version 2 or later. For full details about the license, please check the LICENSE.md file or https://ckeditor.com/legal/ckeditor-oss-license.

testing_blog_1 development dependencies

@ckeditor/ckeditor5-core @ckeditor/ckeditor5-dev-utils @ckeditor/ckeditor5-dev-webpack-plugin @ckeditor/ckeditor5-theme-lark css-loader postcss-loader raw-loader style-loader terser-webpack-plugin webpack webpack-cli

FAQs

What is testing_blog_1?

The classic editor build of CKEditor 5 – the best browser-based rich text editor. Visit Snyk Advisor to see a full health score report for testing_blog_1, including popularity, security, maintenance & community analysis.

Is testing_blog_1 popular?

The npm package testing_blog_1 receives a total of 2 weekly downloads. As such, testing_blog_1 popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is testing_blog_1 well maintained?

We found indications that testing_blog_1 is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is testing_blog_1 safe to use?

The npm package testing_blog_1 was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 30 October-2024, at 11:34 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

testing_blog_1

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

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (2)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Readme

CKEditor 5 classic editor build

Documentation

Quick start

License

testing_blog_1 dependencies

testing_blog_1 development dependencies

FAQs

What is testing_blog_1?

Is testing_blog_1 popular?

Is testing_blog_1 well maintained?

Is testing_blog_1 safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (2)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

CKEditor 5 classic editor build

Documentation

Quick start

License

testing_blog_1 dependencies

testing_blog_1 development dependencies

FAQs

What is testing_blog_1?

Is testing_blog_1 popular?

Is testing_blog_1 well maintained?

Is testing_blog_1 safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues