The package has a clear README, a matching source repository, and a small dependency surface. Its maintenance appears to have stopped long ago, while the repository lacks security scanning and the single-person project has limited continuity evidence.
40%
Total Score
25
100
75
75
The latest release was published in May 2016, and there have been no releases in the last 12 months despite the package being over 10 years old. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history showing no activity since May 2016.
Only one registry maintainer is listed. The matching user-owned repository provides some continuity, but there is still little maintainer redundancy.
Composer is used for builds, which is appropriate, but no security scanning tools are present. This is a maintenance and transparency gap, though not severe on its own.
The linked repository has no security policy. For an old package that handles cloud communications, this leaves vulnerability reporting and response expectations unclear.
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.