Its MIT declaration, single runtime dependency, and lack of install scripts reduce avoidable adoption friction. The organization-owned repository matches the package and is neither archived nor deprecated, but the tiny footprint limits confidence in long-term support.
42%
Total Score
50
100
78
75
The latest release was published about seven years ago, and there have been no releases in the past 12 months. This is strong evidence of abandonment for a dependency that may need compatibility or security updates.
There were zero commits and zero active maintainers in the past three months, consistent with the roughly seven-year release gap. This materially increases abandonment risk.
The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides little supporting evidence of community review or maintenance capacity.
Composer build tooling is present, but no security scanning tooling was detected. The missing scanning is a hygiene concern, while the long inactivity remains the larger issue.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap for an API client dependency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3 | — | — |
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.