The package is small and clearly tied to its matching repository, with a declared MIT license, release notes, and no install scripts. Its long-standing inactivity leaves substantial maintenance and compatibility risk for a payment integration.
38%
Total Score
25
100
67
75
Only two releases were published, both in May 2018, with no release in roughly eight years. That provides little evidence of ongoing maintenance or compatibility work.
The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the last push in May 2018 and strongly indicating abandonment.
Only one registry publishing account is listed. Because the project is user-owned, this is not inherently abnormal, but it leaves little visible publishing redundancy alongside the inactive repository.
The repository is not marked archived, which is a positive sign, but its last push was in May 2018 and does not offset the absence of current activity.
The linked repository has no security policy. This is a transparency and vulnerability-reporting gap, although it is secondary to the much older maintenance history.
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.