Usable with caveats: it is a licensed, stable package with tests, documentation, and a matching source repository, but it has had no release or commit activity for about 11 years. Its age and inactive maintenance make compatibility and future support concerns.
52%
Total Score
50
78
75
The repository recorded zero commits and zero active maintainers during the last three months, consistent with approximately 11 years of inactivity. This is the strongest adoption concern because payment integrations may need ongoing compatibility fixes.
The latest release was published on June 5, 2015, and there have been no releases in the last 12 months. This long release gap is a meaningful maintenance concern for a payment integration.
The repository has 2 stars, 0 forks, and 1 watcher. Low popularity is only supporting evidence, but it offers little indication of a broad community able to maintain or review the package.
Composer is used as the build tool, but no security scanning tools are present. The missing scanning automation is a transparency gap, though the repository has no workflows that introduce additional workflow risk.
The repository is not archived, but its last push was on June 5, 2015. The unarchived status helps, yet it does not offset the very long period without visible maintenance.
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.