mcustiel/phiremock-codeception-module

Maintainerscaution

Only one account has registry publish access. That is a meaningful continuity risk for a user-owned project because release responsibility is concentrated in a single person.

Project backingcaution

The registry namespace and repository owner match, but the project is user-owned rather than organization-backed. This supports identity consistency while offering less redundancy if the maintainer becomes unavailable.

Release historycaution

The project has existed for about six years with 12 releases and a latest release about five months ago, but only one release appeared in the last 12 months, indicating a slower current cadence.

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. Although a release was published about five months ago, the absence of recent repository activity raises a genuine maintenance concern.

Repo issue activitycaution

The repository has only one open issue and no pull requests, with no recent issue or pull-request flow. This is not severe by itself for a small package, but it provides limited evidence of an active maintenance community.