Package Health/contributte/elasticsearch

contributte/elasticsearch

Organization backing, matching source, repository tests, release notes, and a security policy provide useful maintenance and transparency evidence. MIT licensing and no install scripts reduce adoption friction, while the small user base limits independent signals of maturity.

Latest v0.6.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for over 8 years but has only 8 releases, with one release in the last 12 months and a median interval of about 344 days. This indicates slow maintenance rather than abandonment because a recent release exists.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. This is a meaningful maintenance concern, though it is partly offset by the recent release and recent repository push.

Repo issue activity

There is one open issue and two open pull requests, but none were created or merged in the last month. This suggests limited current community activity without proving abandonment.

Repo popularity

The repository has 8 stars and 5 forks, indicating a small user and contributor footprint. Low popularity is supporting caution rather than a standalone health verdict.

Repo tooling

The project uses Composer and Make for build tasks, but no security scanning tools were detected. The missing scanning layer is a modest transparency and hygiene gap.