Package Health/pfefferle/wordpress-blockroll

pfefferle/wordpress-blockroll

This release appears suitable to depend on, with a matching and actively maintained source repository, a stable non-prerelease version, strong recent commit and pull-request activity, repository tests, a license file, and no deprecation or archived-repository indicators. The main risks are that the package is very young at 16 days old, all recent commits come from one contributor, and the repository lacks an explicit security policy and top-level workflow permission declarations; these warrant monitoring but do not outweigh the current maintenance and transparency evidence.

Latest 1.1.0

Packagist

78%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry maintainer is listed, which creates publishing continuity risk, although the matching source repository shows active ownership by the same individual.

Project backing

The repository is owned by an individual user rather than an organization, so the single-contributor concentration is not compensated by visible organizational backing.

Release history

The package is only 16 days old and has two releases, so its long-term maintenance and release practices are not yet established.

Repo bus factor

All 85 recent commits came from one contributor, so maintenance is highly concentrated and could be vulnerable to that contributor becoming unavailable.

Repo tooling

Composer is used as a build tool, but no security scanning tooling was detected, leaving a modest supply-chain hygiene gap.