Healthy and usable, with some maintenance and security-process caveats. The release has strong documentation, tests, release notes, and a clear source repository, but recent commit activity is absent and the repository lacks a security policy and explicit workflow permissions.
76%
Total Score
75
100
88
80
There is one registry publishing maintainer. That is a modest bus-factor concern for a user-owned project, although the repository and recent release activity provide some compensating evidence.
The repository recorded zero commits and zero active maintainers in the last 3 months, which is a real maintenance concern, though the recent release and repository push show the project is not clearly abandoned.
Composer build tooling is present, but no security scanning tools were detected, leaving a security-hygiene gap.
The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.
The CI workflow does not declare top-level token permissions. No write permissions were observed, but explicit least-privilege settings would provide stronger workflow security hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
omnipay/common Version ^3 | — | — |
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.