sallycms/be-search

Its small, focused artifact has a modest dependency surface and no install-time scripts. Organization ownership and a matching repository improve traceability, but this release should be treated as legacy software.

Latest v3.0.0

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published more than 10 years ago, with no releases in the last 12 months. That long lapse is strong evidence of abandonment risk despite a history of nine releases.

Repo commit activity

There were no commits or active maintainers in the last three months, and the repository was last pushed nearly 10 years ago. This is a substantial abandonment risk.

Package scaffolding

The package has no README, while tests and a changelog are absent from the artifact and repository; the latter two are normal for published packages. Missing consumer documentation is a minor transparency concern for a backend add-on.

Repo popularity

The repository has zero stars and one fork, providing little supporting evidence of adoption or an active user community. Popularity is only supporting evidence, so this is a modest concern.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tooling was detected. The missing scanning is a hygiene gap rather than a standalone reason to reject the release.