The package includes a usable README, repository tests, and clear MIT licensing. However, no releases or commits for over eight years and no security policy make maintenance and support uncertain.
52%
Total Score
50
83
50
The latest release was published over eight years ago, with no releases in the last 12 months. This is a substantial maintenance concern for a payment integration, despite a history of 10 releases.
The repository had no commits and no active maintainers in the last three months, consistent with the last push being over eight years ago. This materially raises abandonment and compatibility risk.
There has been no issue or pull-request activity in the last month, with one issue still open. The quiet tracker reinforces the lack of recent maintenance evidence, though it is weaker evidence than the absent commits.
The project uses Composer for builds, but no security scanning tools were detected. For a payment-related integration, the absence of automated security scanning is a meaningful hygiene gap.
No repository security policy was found. That reduces transparency about vulnerability reporting and response, especially for a package handling payment flows.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
payum/core Version ^1.3.6 | — | — |
mobiledetect/mobiledetectlib Version ^2.8 | — | — |
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.