The package is small and clearly documented, with a matching repository and no install-time scripts. However, its last release and repository activity are from 2019, and the license declaration conflicts with the detected file.
43%
Total Score
50
75
75
Only two releases exist, with none in the last 12 months; the latest was published about seven years ago. This is strong evidence of abandonment risk for a deployment integration.
There were no commits or active maintainers in the last three months, consistent with the repository's last push in 2019. This materially increases abandonment risk.
A GPL-3.0+ manifest declaration and a detected GPL-2.0 license file do not match. The package is licensed, but the discrepancy creates a genuine legal and transparency concern.
Composer build tooling is present, but no security scanning tooling was detected. That is a secondary hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This adds a transparency gap for a package involved in deployments.
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.