basemotive/phersist

The package is small, documented, and has a focused dependency profile. Consumer safeguards and independent maintenance capacity are limited, so future support depends heavily on its current owner.

Latest v0.6.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by the individual account basemotive rather than an organization. This is consistent with the single-contributor activity and provides no organizational handoff capacity.

Repo bus factor

One contributor made all commits in the last 3 months, giving the project a 100% top-contributor share. Because the backing owner is an individual, there is little visible maintenance redundancy.

Repo commit activity

The repository has 3 commits in the last 3 months and only one active maintainer. Recent activity exists, but the volume is modest for a package receiving frequent releases.

Repo tooling

Composer is used as a build tool, but no security scanning tools were detected. This is a process gap for a database-oriented library, though it is not evidence of a security defect by itself.

Security policy

The repository has no security policy. That reduces transparency about vulnerability reporting and response expectations, particularly for a library that handles database operations.