Documentation, licensing, and release notes are in place, and the repository remains available with a security policy. However, the package has had no registry release since October 2017 and no commits in the last three months, so future compatibility support is uncertain.
58%
Total Score
50
100
83
100
Only two releases exist, with the latest published in October 2017 and none in the last 12 months. This long release gap materially raises abandonment and compatibility risk.
The project is owned by an individual matching the registry namespace, so there is no organization backing to provide broader maintenance capacity.
The repository recorded zero commits and zero active maintainers in the last three months. The repository is not archived, but current development activity is absent.
There were no new or closed issues or pull requests in the last month, while six issues and two pull requests remain open. This suggests limited recent maintenance attention.
Composer is used for the build, but no security scanning tool was detected. This is a modest supply-chain hygiene gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.