Package Health/makbulut/laravel-aerospike

makbulut/laravel-aerospike

Clear documentation, licensing, and package ownership make the release understandable to adopt. Its maintenance evidence is stale, with no commits or releases for about eight years and no security policy or scanning.

Latest v1.3

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was on July 5, 2018, and there were no releases in the last 12 months. This long release gap is a substantial abandonment concern despite the package having four historical releases.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the last repository push being about eight years ago. This is the strongest evidence that maintenance has effectively stopped.

Project backing

The registry namespace and repository owner match, and the project is owned by an individual rather than an organization. This is consistent ownership, but it provides limited maintenance capacity evidence.

Repo issue activity

There is one open issue, with no new or closed issues or pull requests in the last month. This shows little current project interaction but is secondary to the longer-term inactivity.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. The missing security tooling is a meaningful hygiene gap for a dependency that handles application caching.