Package Health/teppokoivula/search-engine

teppokoivula/search-engine

Clear documentation, licensing, and a predictable release record support long-term use. Security guidance is absent, and recent repository activity is sparse, which makes future support less certain.

Latest 0.40.3

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so the concentrated maintainer and contributor activity is not offset by visible organizational backing.

Repo bus factor

One contributor made all commits during the last 3 months, leaving maintenance continuity concentrated in a single person. The long release history partly offsets this, but no second active contributor is shown.

Repo commit activity

The repository recorded one commit in the last 3 months. Although the recent release history shows ongoing publishing, this low observed code activity is a maintenance caution.

Repo tooling

Composer is used for builds, which fits the package ecosystem. No security-scanning tooling was detected, leaving a modest transparency and assurance gap.

Security policy

The repository has no security policy. This does not show a vulnerability, but it gives maintainers and consumers no documented process for reporting security issues.