The package is clearly identified, has a usable README, and includes release notes for this version. Its single-maintainer project shows little current oversight, making future fixes and compatibility support uncertain.
42%
Total Score
25
79
75
The package has eight releases since July 2019, but its latest release was in May 2020 and it has had no releases in the last 12 months. This long release gap is a substantial abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long period without releases. No provided activity signal compensates for this lack of recent maintenance.
Only one registry account can publish the package, which leaves little visible publishing redundancy. The repository is user-owned rather than organization-backed, so this is a meaningful resilience concern.
The repository uses Composer tooling, but it has no reported security scanning. That is a modest transparency and maintenance gap, not a severe risk by itself.
The repository has no security policy. For a payment-related library, this reduces transparency about vulnerability reporting and response, and no other provided signal compensates for it.
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.