@wordpress/block-serialization-default-parser

v5.14.0

Block serialization specification parser for WordPress posts. For more information about how to use this package see README

Latest version published 12 days ago

License: GPL-2.0-or-later

NPM

GitHub

Package Health Score

95 / 100

security
No known security issues
popularity
Popular
maintenance
Healthy
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
5.14.0	\|	12/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.13.0	\|	11/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.58.0	\|	05/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.10.2	\|	04/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.9.1	\|	02/2021		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

Popular

Weekly Downloads (62,083)

GitHub Stars: 10.67K
Forks: 4.25K
Contributors: 390

Direct Usage Popularity

The npm package @wordpress/block-serialization-default-parser receives a total of 62,083 downloads a week. As such, we scored @wordpress/block-serialization-default-parser popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @wordpress/block-serialization-default-parser, we found that it has been starred 10,674 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: No
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 390
Funding: No

A good and healthy external contribution signal for @wordpress/block-serialization-default-parser project, which invites more than one hundred open source maintainers to collaborate on the repository.

How about a good first contribution to this project? It seems that @wordpress/block-serialization-default-parser is missing a README file.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 6.07K
Open PR: 1.49K
Last Release: 12 days ago
Last Commit: 2 days ago

Further analysis of the maintenance status of @wordpress/block-serialization-default-parser based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @wordpress/block-serialization-default-parser demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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.

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: >=18.12.0

Age: 6 years
Dependencies: 1 Direct
Versions: 155
Install Size: 166 kB
Dist-tags: 14
# of Files: 19
Maintainers: 23
TS Typings: No

@wordpress/block-serialization-default-parser 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.

Not sure how to use @wordpress/block-serialization-default-parser?

To help you get started, we've collected the most common ways that @wordpress/block-serialization-default-parser is being used within popular public projects.

WordPress / gutenberg / test / integration / full-content / full-content.spec.js View on Github

it( basename, () => {
			const {
				filename: htmlFixtureFileName,
				file: htmlFixtureContent,
			} = getBlockFixtureHTML( basename );
			if ( htmlFixtureContent === null ) {
				throw new Error(
					`Missing fixture file: ${ htmlFixtureFileName }`
				);
			}

			const {
				filename: parsedJSONFixtureFileName,
				file: parsedJSONFixtureContent,
			} = getBlockFixtureParsedJSON( basename );
			const parserOutputActual = grammarParse( htmlFixtureContent );
			let parserOutputExpectedString;
			if ( parsedJSONFixtureContent ) {
				parserOutputExpectedString = parsedJSONFixtureContent;
			} else if ( process.env.GENERATE_MISSING_FIXTURES ) {
				parserOutputExpectedString = JSON.stringify(
					parserOutputActual,
					null,
					4
				) + '\n';
				writeBlockFixtureParsedJSON( basename, parserOutputExpectedString );
			} else {
				throw new Error(
					`Missing fixture file: ${ parsedJSONFixtureFileName }`
				);
			}

View more ways to use @wordpress/block-serialization-default-parser

@wordpress/block-serialization-default-parser dependencies

@babel/runtime

FAQs

What is @wordpress/block-serialization-default-parser?

Block serialization specification parser for WordPress posts. Visit Snyk Advisor to see a full health score report for @wordpress/block-serialization-default-parser, including popularity, security, maintenance & community analysis.

Is @wordpress/block-serialization-default-parser popular?

The npm package @wordpress/block-serialization-default-parser receives a total of 62,083 weekly downloads. As such, @wordpress/block-serialization-default-parser popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @wordpress/block-serialization-default-parser well maintained?

We found that @wordpress/block-serialization-default-parser demonstrated a healthy version release cadence and project activity. It has a community of 390 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is @wordpress/block-serialization-default-parser safe to use?

The npm package @wordpress/block-serialization-default-parser 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 22 December-2024, at 21:25 (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