The MIT license, clear README, stable version, and matching repository provide useful transparency. Maintenance is the main concern: no releases in about two years and no commits in the last three months. The package is not deprecated or archived, but its small user and contributor base limits confidence.
58%
Total Score
63
100
83
88
The registry has one publishing maintainer. That is a thin publishing base for a user-owned project and increases continuity risk when combined with inactive recent release activity.
The repository is owned by an individual user rather than an organization, so the single registry maintainer and limited project backing represent a genuine continuity concern.
The package has 12 releases, but none in the last 12 months and its latest release was about two years ago. This indicates materially slowed maintenance for a library integration dependency.
The repository recorded zero commits and zero active maintainers in the last three months. This supports the concern that active maintenance has weakened.
The repository has one star, zero forks, and one watcher. Low popularity is only supporting evidence, but it offers little external adoption signal to compensate for the thin maintenance base.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version >=5.0.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.