The package has a small user-owned project with no tests, security policy, or security scanning. Its last release and commit were about 9 years ago, making long-term maintenance the main concern despite a matching repository, stable version, MIT license, and no install scripts.
38%
Total Score
0
100
78
83
Only two releases exist, with none in the last 12 months and a median interval of about 3 years. This strongly limits evidence of ongoing maintenance.
There were no commits and no active maintainers in the last 3 months, consistent with the last push being about 9 years ago. This is strong evidence of abandonment risk for a library dependency.
The repository has only 4 stars and 1 fork, providing little community evidence or backup if maintenance is needed. Popularity is supporting evidence, so this reinforces rather than determines the assessment.
Composer build tooling is present, but no security scanning tools were detected. For an SDK handling payments, this is a meaningful transparency and maintenance gap.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in a payment-related SDK.
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.