The MIT license, README, tests, changelog, and single runtime dependency provide a clear, lightweight package structure. The release and repository records are too stale to provide confidence in current compatibility or bug-fix support.
40%
Total Score
25
100
70
75
The latest release was published about 13 years ago, with no releases in the last 12 months; the four-release history is concentrated in a very short period. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and indicating no observed current maintenance.
The registry lists one maintainer. That is not inherently unhealthy for a small package, but it leaves limited visible publishing capacity when combined with absent recent release and commit activity.
The linked repository is not archived, which is a positive counter-signal, but its last push was about 10 years ago and does not offset the lack of recent activity.
The repository has no security policy. This is a transparency and issue-reporting gap, though it is secondary to the much stronger evidence of stale maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzle/guzzle Version ~3.0 | — | — |
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.