There is no security policy or automated security scanning, leaving limited transparency around vulnerability handling. The single release and no commits in over two years also suggest abandonment risk, while the repository does include a usable README and a GitHub release.
35%
Total Score
0
100
63
75
This is the package's only release, published over two years ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance for a payment integration.
There were no commits and no active maintainers in the last three months. Combined with the old release history, this materially raises abandonment risk.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository clearly documents this published package.
The repository uses Composer, but it has no security scanning tools. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository is not archived, which is a positive sign, but its last push was over two years ago. The non-archived status does not compensate for the observed inactivity.
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.