The repository has no security policy, and its minimal four-file tree offers little evidence of development practice. The MIT declaration, README, and lack of install scripts are positives, but they do not offset the long inactivity.
44%
Total Score
71
67
The package has had three releases, but none in the last 12 months and no release since November 2022. This is a substantial abandonment concern for a dependency.
The artifact and repository contain only four files, including a README and Composer manifest. This is transparent but provides little visible project structure or maintenance evidence.
The linked repository name does not match the package and its README does not mention the package, so ownership of the published package is difficult to verify.
The repository is not archived, which is a positive, but it was last pushed in November 2022. The lack of recent source activity reinforces the stale release history.
No security policy is present in the repository. For a package that handles Elasticsearch integration, this reduces transparency around vulnerability reporting and maintenance expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
elasticsearch/elasticsearch Version ^7.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.