The package has a clear README, an MIT declaration, and only one runtime dependency. Recent repository work is concentrated in one contributor, and no security policy is provided.
68%
Total Score
67
100
88
83
The repository is owned by an individual account rather than an organization, so the single-contributor maintenance concentration is not offset by visible organizational backing.
The package has 103 releases, but none in the last 12 months and its latest registry release was over a year ago. Recent repository commits partly offset the release gap, but the published package appears inactive.
One contributor made all six commits in the last three months, leaving no demonstrated contributor redundancy and increasing continuity risk.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest process gap rather than evidence of unsafe code.
The repository has no security policy. For a package handling banking and payment APIs, this is a meaningful transparency and maintenance 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.