lsys/sphinxclient

The tiny README offers little integration guidance, while the repository has no security policy or scanning. Apache-2.0 licensing and a small runtime dependency footprint reduce adoption friction, but do not provide current maintenance assurance.

Latest 0.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has made only one release, on June 28, 2020, with no releases in the last six years. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and materially weakening maintenance confidence.

Package scaffolding

A README is present, but it is only 20 characters and provides minimal consumer guidance. The absence of published tests and a changelog is normal packaging practice and is not itself a concern.

Repo tooling

Composer is used for the build, which is appropriate, but no security-scanning tools are configured. This is a modest assurance gap rather than evidence of unsafe behavior.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This adds transparency risk, especially for a package with no recent maintenance evidence.