Clear licensing, a focused file tree, tests, and a usable README support adoption. Maintenance evidence is limited, so pin this version and expect to own fixes if the payment provider changes.
58%
Total Score
50
100
83
75
The repository is owned by an individual user, matching the registry namespace. This is consistent ownership context, but it does not provide organizational maintenance capacity.
The package has made only one release, about 2 years and 6 months ago, with none in the last 12 months. That limits evidence of active maintenance for a payment integration.
There were zero commits and zero active maintainers in the last three months. Combined with the single-release history, this is meaningful evidence of limited ongoing maintenance.
The repository has no stars, forks, or watchers. This is weak supporting evidence rather than a verdict, but it provides no external adoption signal.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^3.2 | — | — |
php-http/guzzle7-adapter Version ^1.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.