Its documentation, license, Composer metadata, and source repository support basic adoption. The long-stalled release and commit history, limited repository traction, and lack of security tooling make maintenance and future compatibility uncertain.
42%
Total Score
0
71
75
The latest release was published in October 2015, with no releases in nearly 11 years and none in the last 12 months. This is strong evidence of abandonment risk for an API client.
The repository had zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. The repository is not archived, but it shows no recent maintenance.
The repository has 0 stars, 1 fork, and 2 watchers, indicating very limited visible adoption and little supporting community activity. Low popularity alone is not decisive, but it provides no meaningful counterweight to the inactivity.
Composer build tooling is present, but no security-scanning tools were detected. For a library handling API credentials, that leaves a modest transparency and maintenance gap.
The repository has no security policy. This is a transparency gap, although the package's license, README, and source repository provide some compensating documentation.
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.