The package is licensed, documented, tested, and clearly tied to an organization-owned repository. Its small user base and lack of security policy add modest transparency concerns, while its age makes future compatibility uncertain.
42%
Total Score
50
75
83
The last release was about 10 years ago, with no releases in the past 12 months. This is strong evidence of abandonment risk, although the package has a coherent release history with four releases.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the last push occurring about 10 years ago. No provided maintenance signal compensates for this prolonged inactivity.
The repository has zero stars and forks and only two watchers, indicating limited visible adoption. Popularity is supporting evidence and does not independently determine health.
Composer build tooling is present, but no security scanning tools were detected. This is a modest hygiene gap, not a standalone dependency risk.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This matters more for an API client but is secondary to the package's prolonged inactivity.
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.