texditor/blockify-php

The MIT license, focused dependency set, and matching repository make adoption straightforward. A single active contributor and no security policy leave maintenance depth and vulnerability reporting less established.

Latest 2.2.0

Packagist

79%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. This is not decisive because repository activity confirms that the same project owner is actively publishing and maintaining the package, but it leaves little publishing redundancy.

Project backing

The registry namespace and repository are owned by the same individual account, and no organization backing is shown. This is consistent ownership but provides no organizational handoff capacity.

Repo bus factor

One contributor holds 100% of commits over the last three months, creating a clear handoff and continuity risk for a user-owned project.

Repo commit activity

Six commits were made in the last three months, showing recent activity, but all came from one active maintainer.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency gap rather than evidence of unsafe code.