The package is documented and licensed, and organizational ownership provides some continuity. Its single release is about ten years old and the repository has had no commits in about nine years, so adoption carries substantial abandonment risk.
35%
Total Score
50
38
Only one release exists, published about ten years ago, with no releases in the last 12 months. This strongly limits evidence that the package is maintained for current dependencies.
The repository recorded no commits and no active maintainers in the last three months, consistent with the last push being about nine years ago. No provided activity signal compensates for this maintenance gap.
The artifact includes a short README, which helps basic consumer understanding, but neither the package nor repository has tests or a changelog. Missing tests are normal packaging practice, while the lack of repository tests reduces confidence in ongoing maintenance.
The repository name matches the package, but the README does not mention the package name. That leaves some uncertainty about repository-to-package alignment despite the matching repository name.
Composer is used as the build tool, but no security-scanning tooling was detected. This is a hygiene gap rather than evidence that the release is unsafe by itself.
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.