It has clear documentation, tests, a changelog, and a matching source tree. The workflow leaves actions unpinned, while the project has no security policy or scanning, so future maintenance needs extra care.
58%
Total Score
50
83
50
The latest release was in June 2023, with no releases in the following three years and three months. Only two releases exist, indicating limited ongoing maintenance despite a reasonable initial interval.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. This raises the risk that compatibility or payment-service changes will not be addressed promptly.
Composer build tooling is present, but no security scanning tools were detected. That is a meaningful hygiene gap for a payment SDK, although it is not evidence of unsafe code by itself.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This reduces transparency for a package handling payment integrations.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but both of its two action references are unpinned. That weakens build reproducibility and supply-chain protection without making the workflow dangerous on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.0.1 | — | — |
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.