bepo/turbo-suggest

Clear licensing, tests, documentation, and a small runtime dependency keep the package maintainable to adopt. Its single-person ownership, small community, absent security policy, and no commits in the last three months leave less margin for ongoing support.

Latest 0.1.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry maintainer is listed, which creates a limited publishing and support capacity for a user-owned project.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. Although it was pushed recently, the measured inactivity raises ongoing maintenance risk.

Repo popularity

The repository has 3 stars, no forks, and no watchers. Popularity is only supporting evidence, but these counts provide little external validation or visible community resilience.

Security policy

The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented.

Version stability

Version 0.1.2 is not a stable major release, so compatibility expectations are weaker even though it is not marked prerelease.