38%
Total Score
unhealthy
A single release about three years ago and no recent repository commits point to strong abandonment risk.
The package has only one release, published about three years ago, with no releases in the last 12 months. This is strong evidence of stagnation for a dependency that may need compatibility fixes.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no recent maintenance capacity.
The repository has 1 star, 0 forks, and 1 watcher. Popularity is not decisive, but this provides little community evidence to compensate for the lack of maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence of malicious behavior.
The repository has no security policy. This is a transparency and response-process gap, although the small package scope and absence of other security findings limit its weight.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
hyperf/elasticsearch Version ^2.2 | — | — |
elasticsearch/elasticsearch Version ^7.0.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.