The package includes tests, a usable README, and matching MIT licensing. It has no security policy or scanning tools, leaving maintenance and security practices less transparent.
40%
Total Score
25
71
50
The package has had no release in about five years: four releases total, none in the last 12 months. This is strong evidence of abandonment for a payment integration library.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
One registry maintainer is a thin publishing base, although the repository is user-owned rather than organization-owned, so there is no provided backing signal to offset the concentration.
The repository has zero stars and forks and only one watcher, providing no supporting evidence of broad community adoption. Popularity is supporting evidence, so this reinforces but does not determine the result.
Composer is used as a build tool, but no security scanning tools are configured. That weakens automated review practices without showing a direct release failure.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ~2.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.