juzaweb/membership

It includes a readable package description, an MIT declaration, release notes, and only one runtime dependency. However, no registry release has appeared for over two years and the repository recorded no commits or active maintainers in the last three months; workflow dependencies are also unpinned.

Latest 1.0.3

Packagist

57%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by a personal GitHub account rather than an organization, so there is no provided evidence of organizational backing to offset the thin recent activity.

Release history

The package has four releases, but its latest release was over two years ago and it had no releases in the last 12 months. That is a meaningful maintenance and freshness concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last year, this raises abandonment risk despite the recent push timestamp.

Repo tooling

The repository uses Composer for builds, but no security scanning tools are present. This is a modest transparency and hygiene gap, not evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations unspecified.