lifo/autocomplete-bundle

The latest release is about a year old, and no commits were recorded in the last three months. A single maintainer and no security policy or scanning reduce long-term confidence, though the repository is active, licensed, unarchived, and clearly matches the package.

Latest v2.1.2

Packagist

65%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing maintainer is listed, leaving limited visible publishing redundancy. The repository is user-owned rather than organization-backed, so there is no provided backing signal to offset that thin maintainer base.

Package scaffolding

The package includes a substantial README, while the absence of tests and a changelog is normal for a published artifact and is not treated as a gap here. Repository-level test and changelog support is not present, so this provides only limited project transparency.

Release history

The package has 10 releases over about 4 years, but only one release in the last 12 months; the latest release is about a year old. This indicates a modest, currently slow release cadence rather than abandonment by itself.

Repo commit activity

No commits and no active maintainers were recorded in the last three months. The recent release and repository push compensate for abandonment risk somewhat, but current development activity remains weak.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence that the package is unsafe.