A clear README, automated tests, and organization-backed ownership make the package easier to understand and maintain. Its nearly ten years without a release or repository activity leaves substantial abandonment risk, with no security policy adding a smaller transparency gap.
52%
Total Score
50
75
50
The package has had no release in nearly ten years and none in the last 12 months, despite five historical releases. This is strong evidence of abandonment risk, though the package may be intentionally stable.
There were no commits and no active maintainers in the last three months, consistent with the last repository push being in December 2016. This materially increases the risk that defects and compatibility problems will go unanswered.
Composer build tooling is present, but no security scanning tooling was detected. That is a modest transparency and maintenance gap rather than a standalone adoption blocker.
The linked repository is not archived, although it was last pushed in December 2016. The unarchived state is positive, but the old push date does not demonstrate current maintenance.
The repository has no security policy, leaving no published process for reporting or handling vulnerabilities. This is a real but secondary concern alongside the much older maintenance record.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.2 | — | — |
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.