larawei/serverchan

Basic integration is documented, and the MIT license plus small dependency footprint reduce adoption friction. However, the project has had no commits or new releases for about eight years, with no tests or security policy, so maintenance risk is substantial.

Latest 0.01

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about eight years ago, with no releases in the last 12 months. That strongly limits evidence of ongoing maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its last push in 2018. This is strong evidence of abandonment risk.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. For a small package this is a hygiene gap rather than a severe risk, though it adds to the limited maintenance evidence.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. Combined with the lack of recent activity, this weakens transparency and supportability.

Version stability

Version 0.01 is not a stable major release, and the package has no later releases to show maturation or compatibility work.