It is licensed, has a matching organization-owned repository, and has no runtime dependencies. The tiny artifact and lack of install scripts limit integration and installation complexity, but the maintenance evidence is too weak for a dependable dependency.
42%
Total Score
50
100
71
75
The package has had only two releases, both in January 2015, with no releases in the last 12 months. This long period without registry updates is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old release history, this leaves little evidence of ongoing maintenance.
Composer is used for the build, but no security scanning tools were detected. This is a modest transparency and hygiene gap rather than evidence that the package is unsafe.
The linked repository is not archived and was pushed in December 2023, showing it has not been formally abandoned. However, that is materially older than the assessment and does not show current activity.
The repository has no published security policy. For a small internal installer this is a limited gap, but it reduces transparency about how vulnerabilities would be handled.
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.