Clear documentation, tests, and a stable release history support adoption. Ongoing maintenance and security oversight are limited, with no recent commits and no repository security policy or scanning.
58%
Total Score
0
100
81
50
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push being about four years ago. That materially raises abandonment risk.
The package has five releases over about five years, but none in the last 12 months; the latest release was about four years ago. This indicates a mature but inactive release stream.
The repository uses Composer build tooling, showing basic project tooling, but no security-scanning tools were detected. The missing scanning is a modest oversight gap.
The linked repository is not archived, which preserves a path for future maintenance, but its last push was about four years ago and does not offset the observed inactivity.
No security policy was found in the repository. This weakens the project's process transparency, though it is a maintenance concern rather than evidence that the release is unsafe.
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.