ebrana/elasticsearch

This release appears generally safe to depend on from a maintenance and transparency perspective: it is licensed under MIT, has a substantial 527-file source and package tree, tests, changelog, build tooling, recent release activity, and an active non-archived repository with 31 commits in the last 3 months. The main concerns are that the project is young with only three releases, all recent commit activity comes from one contributor, the repository has no security scanning or security policy, and its popularity is minimal. Organization ownership and a merged pull request provide some compensation for the concentrated contributor base, but the package remains less mature and less resilient than an established dependency.

Latest v1.1.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 182 days old with three releases and a median release interval of about 91 days. This shows ongoing publication but limited maturity and a still-short operating history.

Repo bus factor

One contributor made all 31 commits in the last 3 months, creating a clear single-maintainer continuity risk. The organization-owned repository provides some potential handoff capacity, but no second active contributor is shown.

Repo popularity

The repository has zero stars and forks and only four watchers. Popularity is supporting evidence rather than a verdict, but these counts provide little external validation or community resilience.

Repo tooling

Make and Composer are used for build/development workflows, but no security scanning tools are configured. The build tooling is positive while the missing security automation is a hygiene gap.

Security policy

The repository has no SECURITY.md or other detected security policy. This reduces vulnerability-reporting transparency, although it is not by itself evidence of unsafe code.