Clear licensing, a small dependency set, repository tests, and a documented changelog support practical adoption. The repository lacks a security policy and security scanning, so maintenance risk remains concentrated despite organization backing.
72%
Total Score
83
100
94
75
All five recent commits came from one contributor, creating a real continuity risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tools were detected. That is a maintenance and oversight gap, though not severe on its own.
The repository has no security policy. Consumers have less documented guidance for reporting and handling vulnerabilities, which modestly lowers transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
payum/core Version ^1.5 | — | — |
authorizenet/authorizenet Version ^1.8.1 | — | — |
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.