Organization ownership and a recent repository push provide some continuity. The package also includes tests, a README, and release notes, but there is limited evidence of broad maintenance or hardened publishing practices.
68%
Total Score
75
86
67
The package has existed for about 5.6 years, but only one release appeared in the last 12 months and releases are typically about 13 months apart. That is a meaningful maintenance concern for a payment integration.
All four commits in the last three months came from one contributor, leaving maintenance dependent on a single active individual. Organization ownership offers some handoff capacity, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tools were detected. This is a modest gap rather than evidence of unsafe behavior.
The repository has no documented security policy, leaving vulnerability reporting and response expectations unclear for a payment-related integration.
The audit analyzed only 1 of 2 workflows and failed on 1 file, so coverage is incomplete. All 4 analyzed action references are unpinned, which weakens build reproducibility, although no dangerous trigger, untrusted checkout, script injection, or high-confidence audit finding was reported.
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.