The package is licensed and its repository matches the package, but its maintenance story is weak. It has no tests, README, changelog, or security scanning, leaving consumers with little guidance or assurance.
38%
Total Score
100
72
75
Only two releases were published, both in October 2019, with no release in nearly seven years and none in the last 12 months. This is strong evidence of abandonment for a maintained client library.
The package contains no README, tests, or changelog. Missing tests and changelog are normal for published artifacts, but a missing README is a real usability and transparency gap for a library consumers must integrate.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these figures provide no external sign of adoption or active community support.
Composer is used for the build, which fits the package ecosystem, but no security scanning tools are present. This is a modest transparency gap alongside the broader maintenance concerns.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters more for a library that wraps an Elasticsearch client.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jsq/amazon-es-php Version ^0.3 | — | — |
elasticsearch/elasticsearch Version ^7.3 | — | — |
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.