The MIT license, readable documentation, matching source tree, and no install-time scripts make integration and provenance clearer. However, the project has had no commits or releases since September 2017, with no security scanning or policy.
42%
Total Score
0
67
83
The package has 36 releases but none in the last 12 months, and its latest release was about 9 years ago. This strongly indicates abandonment risk despite its earlier release history.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, while its last push was in September 2017. That lack of current maintenance is a substantial dependency risk.
The repository has 0 stars and 0 forks, with only 1 watcher. Popularity is supporting evidence rather than decisive, but these figures provide no meaningful community-maintenance cushion.
Composer build tooling is present, but no security-scanning tools are configured. The missing scanning is a hygiene and maintenance concern for a payment integration library.
The repository has no security policy. For a payment SDK, 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.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.