The package is licensed, documented, tested, and backed by an organization, with no install-time scripts. Its beta status, repository mismatch, and absent security scanning add uncertainty.
35%
Total Score
50
57
83
The package is nearly 12 years old but has had no release in that period, with zero releases in the last 12 months. This is strong evidence of abandonment risk.
The repository had zero commits and zero active maintainers in the last 3 months. Combined with the stale registry release history, this materially raises abandonment risk.
The repository name does not match the package name and its README does not mention the package. Although organization backing provides some context, the linkage remains questionable.
Composer is used for builds, which fits the ecosystem, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The linked repository is not archived, and it was last pushed in April 2022. This avoids an archival failure, but the old push date does not offset the absent recent release activity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.