The MIT declaration and single runtime dependency keep adoption straightforward, while the repository remains identifiable and unarchived. Maintenance transparency is limited by the absent security policy, single maintainer, and minimal project activity.
42%
Total Score
50
100
60
50
The package has had only 3 releases, with none in the last 12 months, and its latest release was over 7 years ago. This is strong evidence of abandonment risk for a dependency.
One registry maintainer is consistent with a small user-owned project, but there is no provided evidence of a wider maintainer base to reduce single-person continuity risk.
The repository has 0 stars, forks, and watchers. Popularity is supporting evidence rather than a verdict, but these values provide no evidence of a broader user or maintainer community.
The repository is not archived, which avoids the strongest abandonment signal, but its last push was over 7 years ago and does not offset the inactive release history.
The linked repository has no security policy. For a package that sends messages through a runtime dependency, this reduces transparency around vulnerability reporting and response.
We didn't find any vulnerabilities for this package.
| 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.