The MIT license, README, and absence of install-time scripts make the package straightforward to inspect and install. Its very small project has no tests, no security policy, one registry maintainer, and no recent development, leaving payment-provider compatibility and long-term support uncertain.
38%
Total Score
25
70
75
The package has only one release, published nearly 9 years ago, with no releases in the last 12 months. This is strong evidence that the dependency is no longer actively maintained.
The repository recorded no commits and no active maintainers in the last 3 months, and its last push was nearly 5 years ago. The non-archived status does not compensate for this prolonged inactivity.
Only one person has registry publish access, which gives the release a thin publishing base. This is more concerning alongside the absence of recent repository activity, though access records alone do not prove maintenance capacity.
Composer build tooling is present, but no security-scanning tooling was detected. The lack of scanning is a modest hygiene gap rather than evidence that the package is unsafe by itself.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities in a payment integration. No other provided signal compensates for this transparency gap.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.