Package Health/pop-wp-schema/block-content-parser

pop-wp-schema/block-content-parser

This is a generally healthy and actively maintained release: it has over three years of history, 131 releases including 33 in the last 12 months, a stable non-prerelease version, recent repository activity, clear licensing, tests, and a matching source repository owned by an organization. The main concerns are that all 14 commits in the last three months came from one contributor, the repository has little public popularity, and it lacks a security policy and automated security-scanning tooling. These are meaningful resilience and transparency gaps, but they are outweighed by the strong release cadence, current repository, project backing, and coherent package structure.

Latest 19.2.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access, which is a resilience concern, although the linked repository is owned by an organization and the strong release history shows that publishing is currently active.

Repo bus factor

One contributor made all 14 commits in the last three months, creating a genuine continuity risk; organization ownership provides some potential handoff capacity but no second active contributor is observed.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, indicating limited external adoption or review; this is a supporting caution rather than a health verdict because the package is actively released and maintained.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured, leaving a transparency and automated-detection gap.

Security policy

The repository has no security policy, so users are not given a documented vulnerability-reporting process in the repository; the README's email guidance provides partial practical coverage but not a formal policy.