yaoshanliang/phpsms

It has an MIT license, a README, and no install-time scripts. The tiny codebase and absent security policy leave little supporting evidence for long-term maintenance.

Latest v1.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest of only 3 releases was about 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, despite the historically regular early cadence.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the release history showing prolonged inactivity. This materially increases abandonment risk.

Project backing

The package and repository are owned by the same individual account, so the source ownership is consistent. Individual ownership does not provide the capacity or continuity signals an organization might offer.

Repo popularity

The repository has 1 star, 0 forks, and 1 watcher, providing almost no community adoption or external maintenance signal. Popularity is supporting evidence rather than a verdict, but it offers no meaningful compensation here.

Repo tooling

Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a hygiene gap that adds some uncertainty for a package with little other recent activity.