wpelevator/update-client

Usable with caveats: it is actively released, backed by an organization, and has a matching source repository. Adoption carries maintenance risk because all recent commits come from one contributor and the small project has no tests, changelog, or security policy.

Latest 0.8.1

Packagist

72%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package includes a substantial README, but neither the artifact nor repository has tests or a changelog. For a small seven-file library this is a real transparency and maintenance gap, though the README documents usage.

Repo bus factor

One contributor made all 6 commits in the last 3 months, creating a concentrated maintenance risk. Organization ownership provides some ability to hand maintenance off, so this is a caution rather than a severe abandonment signal.

Repo issue activity

There are no new issues or pull requests in the last month, and no pull requests were merged. This gives little evidence of community review or issue handling, although the absence of reported issues is not itself abandonment.

Repo popularity

The repository has zero stars and forks and one watcher, so there is little public adoption evidence. Popularity is supporting evidence rather than a requirement, and the package's active release history is more informative here.

Repo tooling

Composer is used as a build tool, which fits this PHP package, but no security scanning tools are configured. That leaves a modest transparency and assurance gap.