Tests, a useful README, and release notes provide a solid starting point for consumers. The single-maintainer setup, absent security policy, and lack of repository security scanning leave limited ongoing oversight.
57%
Total Score
67
79
75
Only one registry account has publishing access. Because the repository is user-owned rather than organization-backed, this represents a narrow publishing and maintenance base.
The package has only two releases, both published within minutes on the same day, followed by roughly five months without another release. This limited history makes long-term maintenance uncertain.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the short release history, this is meaningful evidence of currently inactive maintenance.
Composer build tooling is present, but no security scanning tools were detected. This weakens automated oversight without independently making the package unsafe to depend on.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities in a payment integration package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^8.0|^9.0|^10.0|^11.0|^12.0|^13.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.