The single-maintainer project is small and has no tests or security scanning. It does include a matching repository, MIT license, release notes, and no install scripts.
57%
Total Score
50
86
83
One registry maintainer is consistent with an individually owned project, but there is no organization backing shown and the repository activity is currently inactive. This leaves limited visible maintenance capacity.
The package has only two releases, with no release in the last 12 months and the latest release published about 15 months ago. This is a meaningful maintenance concern for a payment integration.
The repository recorded no commits and no active maintainers during the last three months, following the latest push about 15 months ago. That indicates currently inactive maintenance.
Composer build tooling is present, but no security scanning tools were detected. For a payment integration, that is a modest transparency and maintenance gap.
The repository has no security policy. This is a hygiene gap for a package handling payment-related integration, though it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^8.0|^9.0|^10.0|^11.0|^12.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.