Package Health/fullpipe/sphinxsearch-bundle

fullpipe/sphinxsearch-bundle

Risky to adopt: it has had only one release, published nearly 13 years ago, and its repository has seen no commits in about 11 years. The package is licensed, documented, and not deprecated or archived, but the long-term lack of maintenance makes compatibility and support uncertain.

Latest v1.0

Packagist

35%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, with no releases in the last 12 months; that release was published nearly 13 years ago. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the repository's last push being about 11 years ago. This is the clearest ongoing-maintenance risk.

Package scaffolding

The package includes a readable README and changelog; the absence of tests in the published artifact is normal packaging practice, while the repository also reports no tests. Documentation helps consumers, but does not offset the lack of recent maintenance.

Repo tooling

The repository uses Composer, showing basic build tooling, but it has no security scanning tools. That is a modest transparency and maintenance gap for an old dependency.

Repository archived

The repository is not archived, but its last push was about 11 years ago. The non-archived status is reassuring administratively, while the old activity is a material abandonment concern.