Clear documentation, tests in the repository, a changelog, and a small dependency set help adoption. However, the package has had no registry releases since May 2021 and no recent repository commits, while maintenance rests with one publisher.
54%
Total Score
33
100
69
83
The package is nearly five years old, has 10 releases, and has had no release in the last 12 months; the latest release was in May 2021. This is strong evidence of abandonment risk for a payment integration.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this materially raises the risk that defects and compatibility changes will go unattended.
Only one account has registry publish access. That is a thin publishing base, and the repository's lack of recent activity provides no compensating evidence of an active broader maintainer group.
The package and repository are both owned by the same individual account, confirming that the source appears connected to the package. It does not provide organization-level continuity if that maintainer stops working on it.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3|^7.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.