Its MIT license, substantial README, tests, and matching repository are reassuring. The small dependency surface and lack of install scripts reduce operational friction, but the package still needs careful replacement planning.
35%
Total Score
75
100
64
83
The package is flagged as borrowing the identity of the much more established `laravel/pail`, with `borrows_lookalike_identity` true. Although artifact overlap is zero, this is a serious adoption and package-selection risk because consumers may have intended the lookalike package.
The package has 49 releases but none in roughly eight years; its latest release was published in February 2018. That long release gap is strong evidence of abandonment risk despite the historical release count.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of recent releases. This materially lowers confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe on its own.
The repository has no security policy. This is a transparency gap for a payment integration package, although the available tests, license, and source repository provide some compensating documentation.
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.