Consumer transparency and maintenance support are limited. The license and package-to-repository match are reassuring, but this old, single-release project is a risky dependency.
40%
Total Score
25
100
63
75
The package has had only one release, published in April 2018, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency that may need ongoing fixes.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the project having been inactive since April 2018. This materially increases maintenance and abandonment risk.
Only one registry publishing account is listed. A single maintainer is not inherently unhealthy, but combined with the absence of recent activity it leaves little visible maintenance capacity.
The artifact includes a README file, but it is empty, and no tests or changelog are present. Missing tests and changelog are normal for published artifacts, while the empty consumer documentation weakens transparency.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these very low adoption indicators provide no additional evidence of community support.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3@dev | — | — |
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.