The package has a long release history, recent activity from three contributors, tests, release notes, and clear licensing. Its repository does not identify or mention this package, and it has no security policy or scanning tools, so verify the source mapping before adoption.
76%
Total Score
100
86
75
The repository name does not match the package name and its README does not mention the package. Although naming differences can occur in organization repositories, the two gaps together make the package-to-source mapping less clear.
Composer is used for builds, but no security-scanning tools were detected. This is a transparency and maintenance-process gap, though it is not evidence of unsafe code by itself.
The repository has no SECURITY.md or other detected security policy. For a payment integration, the absence of a documented vulnerability-reporting process is a meaningful transparency gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.