A complete README, repository tests, and a declared MIT license support adoption and make the package easier to maintain locally. However, no releases or commits were recorded in the last 12 months, so current maintenance is uncertain.
58%
Total Score
67
80
50
Only one registry publishing account is listed, which is a concern for release continuity. The organization-owned repository provides some backing, so this is not by itself evidence of abandonment.
The package has 18 releases, but its latest release was over a year ago and there were no releases in the last 12 months. The clustered early release history shows initial activity but not ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the lack of recent registry releases. This is a meaningful maintenance concern, though the repository is not archived.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package handling payment integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^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.