rkmax/sphinx-client

Risky to adopt: the package has had no release or repository activity for about 11 years, leaving maintenance and compatibility concerns. It is small and transparent enough to inspect, but there is little evidence of ongoing support.

Latest 1.0.1

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in April 2015, with no release in about 11 years. This is strong evidence of abandonment for a dependency intended for ongoing use.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with the repository's last push being about 11 years ago. This is the main maintenance and abandonment concern.

Maintainers

A single registry publishing account is responsible for the package. This is a limited maintainer base, though the repository is user-owned and no organization backing is shown to compensate for that constraint.

Project backing

The registry namespace and repository owner match, which supports that the repository belongs to the publisher. The owner is an individual rather than an organization, so there is no demonstrated institutional backing.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. With no other recent activity, this offers no evidence of active support.