The pre-1.0 version and lack of repository security scanning limit confidence in long-term support. A clear README, declared MIT license, and no install-time scripts are helpful, but not enough to offset the thin maintenance evidence.
34%
Total Score
0
71
75
The package has had no release in about five years, with zero releases in the last 12 months. Six total releases show some history, but the prolonged gap strongly raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap and providing no evidence of current maintenance.
Composer is used for the build, but no security scanning tools are present. This is a modest transparency and maintenance concern rather than a standalone severe risk.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a transparency gap for a payment-integration package.
The assessed release is not a prerelease, which is positive, but it remains on the 0.1 major version and therefore offers less maturity evidence than a stable major release.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/cache Version 5.* | — | — |
illuminate/config Version 5.* | — | — |
illuminate/support Version 5.* | — | — |
illuminate/container Version 5.* | — | — |
gopay/payments-sdk-php Version ^1.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.